JAAS 1.0 with WLS 6.1 SP2 "Exception from LoginContext "

Hi
Iam trying to use JAAS with weblogic 6.1. SP2
In the startweblogic.cmd I have made entries like
-Djava.security.auth.login.config=sample_jaas.config
While Iam executing the code I get the following
exception
No Configuration Class Name Supplied
java.lang.NullPointerException
at javax.security.auth.login.LoginContext.loadLoginModule(LoginContext.j
ava:101)
at javax.security.auth.login.LoginContext.<init>(LoginContext.java:54)
at jsp_servlet.__login._jspService(__login.java:144)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
java.lang.NullPointerException
at jsp_servlet.__login._jspService(__login.java:157)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)

May be you are not pointing at the right location of the file.
Alternatively, you can also enter login config info entry in the JAVA_HOME\jre\lib\security\java.security
file.(please refer to Login Module Developer's guide)
hope this helps
thanks-Venkata
"Sanu Thomas" <[email protected]> wrote:
>
Hi
Iam trying to use JAAS with weblogic 6.1. SP2
In the startweblogic.cmd I have made entries like
-Djava.security.auth.login.config=sample_jaas.config
While Iam executing the code I get the following
exception
No Configuration Class Name Supplied
java.lang.NullPointerException
at javax.security.auth.login.LoginContext.loadLoginModule(LoginContext.j
ava:101)
at javax.security.auth.login.LoginContext.<init>(LoginContext.java:54)
at jsp_servlet.__login._jspService(__login.java:144)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
java.lang.NullPointerException
at jsp_servlet.__login._jspService(__login.java:157)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)

Similar Messages

Error: An attempt was made to load a program with an incorrect format. (Exception from HRRESULT:0x8007000b)

Hi All,
I am trying to install 64 bit addon on SAP9 64 bit client.
But i am getting following error:
Error: An attempt was made to load a program with an incorrect format. (Exception from HRRESULT:0x8007000b)
Please give some solution.

Hi,
Please refer this thread http://scn.sap.com/thread/1523397
Thanks & Regards,
Nagarajan

32 bit Application calling 32 bit DLL "An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)"

Hi,
I am developing an application in visual c# which loads few DLLs.
While loading the DLLs I am getting this error
"An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)"
Strange thing for me is that I don't get this error always. In most of the cases when I uninstall the application and reboot my PC again when I install again then problem is solved for few days.
I have followed several threads all suggests that This error comes either "64 bit exe tries to load 32 dll" or "32 bit exe tries to load 64 bit dll". In my case i made sure that both the
exe and dll are 32 bit.
In Project property I selected Platform and Platform target to x86. But the problem still occurs.
Some body please suggest some solutions and why this problem occur.
Thanks
Sujeet.

Hi,
How do you load the DLLs? I assume you get an exception and do not call the LoadLibrary API function directly. The latter just returns NULL (Intptr.Zero) if you load a library with the wrong bitness. However, in this case, I do not get error 11 (= 0xB =
ERROR_BAD_FORMAT), but I get error 193 (= ERROR_BAD_EXE_FORMAT), so I think something else is going on on your machine.
So, do you get an exception, and which one? Can you catch and examine it? Does it provide details about which library can not be loaded?
An option is using
Process Explorer to find out which library can not be loaded by looking at which libraries are being accessed most recently.
Another option is using Windbg.exe (from the Windows Debugging Tools). By default, it outputs all loaded modules so that the last one your application tries to load should be listed there, too. It should even be listed if it fails to load; at least that
was the case in my tests.
Sometimes, if no path is specified for the dll file, the dll can be loaded from the current directory. So depending on what happened at runtime before the library is being loaded, the current directory could have been changed so that you can get variable
results during debugging.
When you are saying "when I uninstall the application", do you mean your own application on your own PC? Does the problem (also) happen during debugging inside Visual Studio?
Armin

Portal server with WLS 6.1 SP2

Hi,
Has anybody installed Portal server 4.0 with WLS 6.1 with service pack 2. I got
the following problem:
I changed my WLS6.0 to 6.1 sp2 on WinNT.
Starting install Portal 4.0, it went through well. However, I couldnot
start Portal server. Hereis the massege after start Portal server (WLS is
running) :
# Note: Server initialization may take several minutes.
# Please be patient.
<Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from
user.
>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method
weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Press any key to continue . . .
Could you help me to finger out what's wrong.

Rahul, just wanted to thank you for the info. I was having the same
problem, and changing the classpath and capacityincrement worked.
Thanks again,
John
[email protected] (Rahul Prabhu) wrote in message news:<[email protected]>...
Hi,
Modify the 'Set Classpath' in your startPortal.bat as follows:
SET CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic_sp.jar;%WEBLOGIC_HOME%\lib\weblogic.jar;
..all the existing stuff..etc.
You might also need to change the 'capacityIncrement' in your
config.xml to > 0
let me know if it goes thru.
hth,
Rahul
"Tao Huang" <[email protected]> wrote in message news:<3c362c9a$[email protected]>...
Hi,
Has anybody installed Portal server 4.0 with WLS 6.1 with service pack 2. I got
the following problem:
I changed my WLS6.0 to 6.1 sp2 on WinNT.
Starting install Portal 4.0, it went through well. However, I couldnot
start Portal server. Hereis the massege after start Portal server (WLS is
running) :
# Note: Server initialization may take several minutes.
# Please be patient.
<Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from
user.
>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method
weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Press any key to continue . . .
Could you help me to finger out what's wrong.

IIS Plug-in with WLS 6.1 SP2 Connection Pool ?

I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable it ?
2. How do I control the pool size ?
Thanks in advance,
Tim

"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim

VM Crash with WLS 6.1 SP2 JDK 1.3.1 on NT/MSSQL

Has anyone seen this? If we leave the system on for overnight, WLS crashes without
further message. Our setting is 128M, of course it will get out of memory error
if something is asking more than that. Question is:
who is asking for 400 MB in one shot?
P.S. We have internal scheduler threads wake up every 5 minutes to check tasks
thru EJBs.
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested 402653192
bytes
goto finish
cd config\informatica
ENDLOCAL

Thanks, you are right. It's a known bug in JDK 1.3.1 01 and it has been fixed in
JDK 1.3.1 02.
<[email protected]> wrote:
That's the CompileThread asking for 402653192 bytes, so it's probably
has
nothing to do with application, WebLogic or 0x18000008. You can look
at
this bug:
http://developer.java.sun.com/developer/bugParade/bugs/4484290.html
or several other bugs very similar to this one.
Cameron Purdy <[email protected]> wrote:
FWIW - that's hex 0x18000008 ... I'd start by looking through yourcode for
the string "18000" and then grep through the WL code for the ConstantPool
equivalent in the .class files.
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/
"Yicheng Tao" <[email protected]> wrote in message
news:3cb48efe$[email protected]..
Has anyone seen this? If we leave the system on for overnight, WLS
crashes
without
further message. Our setting is 128M, of course it will get out of
memory
error
if something is asking more than that. Question is:
who is asking for 400 MB in one shot?
P.S. We have internal scheduler threads wake up every 5 minutes to
check
tasks
thru EJBs.
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested402653192
bytes
goto finish
cd config\informatica
ENDLOCAL
Dimitri

JMS Messaging Bridge Problems with WLS 8.1 sp2

          Thank you in advance for your help.
          I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
          Q. I have this working wonderfully in an environment without clustering but once
          I try to deploy to a cluster, I am having two major problems.
          1) When the managed servers are restarted, the messaging bridges immediately complain
          about not being able to find the resource adaptor. After I manually un-target
          the messaging bridge from the cluster and re-target them, they find the resource
          adaptor but cannot connect to the source... which leads to my next problem.
          2) The messaging bridges cannot connect to the source destination whether it is
          an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
          see relative:
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
          Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
          Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
          Bridge.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
          is deployed as a migratable.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
          Bridge as a migratable.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
          source configurations are:
          AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          Classpath=null
          ConnectionURL = file:/e:/private/JNDI/eBusDev02
          DestinationType = Queue
          DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
          InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
          ConnectionFactoryJNDIName = jms.oes.MQ-QCF
          .>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
          target configurations are:
          AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          Classpath=null
          ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
          DestinationType = Queue
          DestinationJNDIName = jms/oes/ADV-REPLYQ
          InitialContextFactory = weblogic.jndi.WLInitialContextFactory
          ConnectionFactoryJNDIName = jms/oes/QCF
          .>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
          is successfully initialized.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
          has been successfully initialized as a migratable.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
          Bridge.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
          has been successfully activated..>
          ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
          <Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
          two adapters.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
          Getting source connection.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
          <Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
          and will try again in 15 seconds. (java.lang.NullPointerException)>
          I know the queues are up and I am pretty sure my MQ client configuration is correct.
          Is there anyway to get more information about the NullPointerException or the
          error being encountered?


Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
          If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
          Tom

IIS plug-in config with WLS 8.1 sp2

We are currently migrating from another app server and have run into problems configuring
the IIS plug-in. We have reviewed the e-docs and developer Web pages on how to
configure the plug-in but cannot successfully find information on how to point
a single IIS virtual host to multiple app servers and URIs on WLS. We're trying
to have one IIS ip:port point to many BEA app servers which can then point to
many URIs so that we can distribute load and code updates across several clusters.
Example:
ourdomain.com -> to WLServer1:8010 /app1/uri1
/app2/uri2
WLServer2:8011 /app3/uri3
/app4/uri4
The problem so far has been getting the IISProxy file to point to more than one
application server (JVM Instance) running on the two WLS machines.
Thanks for any help you can offer!

You should provide some more information. Which IP are you binding to on
          WLS? Are you specifying the same IP in the iisproxy.ini for the
          WebLogicHost?
          Show us your configuration for the iisproxy.ini.
          My best bet is that you are specifying a different IP address in the
          iisproxy.ini or perhaps you are specifying a hostname that does not resolve
          to the bound IP on WLS.
          Regards,
          Eric
          "Farhan Kazmi" <[email protected]> wrote in message
          news:[email protected]..
          > I am having a problem with the IIS plugin. It seems that when ever I
          explicitly bind a WL app server to an IP address, the IIS plugin no longer
          forwards requests on the WL. Does any one know the reason why this is
          happening.
          >
          > Note, if I do not bind to an IP address, the plug-in works fine.
          >
          > OK.... I am not even sure if this forum is working!!. I have tried to
          contact to my BEA sales rep but he is gone for the week.
          >
          > I have posted 3 or 4 questions here, and have heard no replies.

Sun Identity Server 6.1 with Weblogic 8.1 sp2

Hi,
I've installed the IS 6.1 with WLS 8.1 sp2 and the agent 2.1.1 and followed the agent configuration guide to configure the xml files (web.xml and weblogic.xml) and agent authenticator.
When I login to the restricted resource, the browser is redirected to the IS server login page. After login, the browser is redirected back to the resource with 403 forbidden.
Is there any step missing? Should I additional add some policy in the IS console? .....
Clive

I have just installed Sun Identity Server 6.2 with WebLogic 8.1 SP3 and am experiencing the same results. Have you resolved this issue in your environment? We are evaluating Portal Server running on a BEA WLS Container and thus do not have Sun Support on the Identity Server Component of this configuration.

Iplanet 6.x, NSAP & WLS 6.1 SP2

This is very strange. I can get NSAPI with iplanet 4.x to come up fine (everything proxies, etc. as it should). When we try to get iPlane 6.x working with NSAPI and WLS 6.1 SP2...nothing..doesn't work. We're running everything on Solaris.
Does anyone have or know of some good documentation that might describe how to get NSAPI working between WLS 6.1 and iPlanet 6...all the examples I've been seeing are mostly Windows paths, .dlls', etc. I'd love to see some working magnus.conf & obj.conf, etc. using WLS6.1 SP2 and iPlanet 6...we're not clustered and we're not using SSL (yet) so it's pretty vanilla.
What's blowing my mind is why iplanet 4.x works and 6.x doesn;t?? I wonder if the differences between the two are really that great. I checked BEA's doc...and like I said...it seemed a bit cryptic...someone told me ther was a typo or two regarding what was to go in magnus or was it obj.conf...I don't recall..it's just frustrating trying to get NSAPI up and running with WLS 6.1 SP2 and iPlanet 6. Any ideas? Thanks!!

Thanks Kumar. Does the syntax change (such as WebLogicCluster=xxxxxxxxxxxxxxx) if
we are running a single instance of WebLogic (a non-clustered environment)?
Thanks,
Doug
Kumar Allamraju <[email protected]> wrote:
In iplanet 6.x
magnus.conf should have
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib=/usr/local/netscape/plugins/libproxy.so
Init fn="wl_init"
and obj.conf should have
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy \
WebLogicCluster="myweblogic.com:7001,yourweblogic.com:7001,\
theirweblogic.com:7001" PathTrim="/weblogic"
</Object>
Pls post the exact errors that you are seeing, so that we can help
Kumar
"Doug E." wrote:
This is very strange. I can get NSAPI with iplanet 4.x to come up fine(everything proxies, etc. as it should). When we try to get iPlane 6.x
working with NSAPI and WLS 6.1 SP2...nothing..doesn't work. We're running
everything on Solaris.
Does anyone have or know of some good documentation that might describehow to get NSAPI working between WLS 6.1 and iPlanet 6...all the examples
I've been seeing are mostly Windows paths, .dlls', etc. I'd love to see
some working magnus.conf & obj.conf, etc. using WLS6.1 SP2 and iPlanet
6...we're not clustered and we're not using SSL (yet) so it's pretty vanilla.
What's blowing my mind is why iplanet 4.x works and 6.x doesn;t?? I wonderif the differences between the two are really that great. I checked BEA's
doc...and like I said...it seemed a bit cryptic...someone told me ther
was a typo or two regarding what was to go in magnus or was it obj.conf...I
don't recall..it's just frustrating trying to get NSAPI up and running
with WLS 6.1 SP2 and iPlanet 6. Any ideas? Thanks!!

WLS 6.1 SP2 NSAPI and iPlanet (Sun One) issues

Hi. I am going nuts with this NSAPI issue. I am working in a Solaris 8 environment,
WLS 6.1 SP2 and iPlanet (Sun One)and NSAPI. I can get everything to work fine
and dandy in aniPlanet 4.1 environment. I can not get it to work in an Iplanet
(Sun One) 6.x environment. It appears that some things work differently between
the versions of iPlanet (ie. things contained in magnus.conf and/or obj.conf).
I have tried moving things, removing things, adding things and nothing seems
to work....it's almost as though the NSAPI, etc. are being ignored.
I've attached my magnus.conf and obj.conf files (I cut and pasted them into a
single file so I could upload it). Can anyone help me out here...I've been working
for weeks on this and can't seem to get any answers.
Thanks!
Doug
P.S. For security purpses I changed the first part of the IP add. in the files
to 1234567, etc.
Thanks
[conf_files.txt]

Hi Doug
U have to put the following section
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="./libproxy.so"
Init fn="wl_init"
into magus.conf
and put the rest into obj.conf
Best Regards
Alex
"Doug E" <[email protected]> wrote:
>
Does anybody know of a good reference document on how to properly install
the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references
that
I have been finding are either incomplete, have typo's and are mostly Windows
oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies,
etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many
of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other,
etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x
then many
of the docs out there are inaccurate. Does anyone know if there is a newer
version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc
from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix
(Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas?
Thanks!
-Doug

WLS 6.1 SP2, iPlanet 6 & NSAPI problems

Does anybody know of a good reference document on how to properly install the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references that
I have been finding are either incomplete, have typo's and are mostly Windows oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies, etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other, etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x then many
of the docs out there are inaccurate. Does anyone know if there is a newer version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix (Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas? Thanks!
-Doug

Hi Doug
U have to put the following section
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="./libproxy.so"
Init fn="wl_init"
into magus.conf
and put the rest into obj.conf
Best Regards
Alex
"Doug E" <[email protected]> wrote:
>
Does anybody know of a good reference document on how to properly install
the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references
that
I have been finding are either incomplete, have typo's and are mostly Windows
oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies,
etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many
of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other,
etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x
then many
of the docs out there are inaccurate. Does anyone know if there is a newer
version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc
from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix
(Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas?
Thanks!
-Doug

ERROR: Error from ejbc: in WLS 6.1 sp2 Win2K

Never had this problem before. Started new project using WLS 6.1 sp2 under Windows
2K Prof., using ANT & get;
ERROR: Error from ejbc:
In EJB NOTiFYEJB, method createUser defined in the remote interface either does
not exist in the bean class, or it is not a public method. Each method in the
remote interface must have a corresponding public method in the bean class.
BUILD FAILED
I saw a posting which referred to a problem with Win2K & an old (1.2) JDK in the
path. I have put C:\bea\jdk131 at the front of my class path but still get this
error.

The problem was nothing to do with classpaths etc.
CMP does not support "Date" types and in my EJB I had Date types, I changed these
to "long" and converted all Dates to number of milleseconds from 1970 and persisted
them to a number column in Oracle.
It was the entries in the weblogic-cmp-rdbms.xml which was the root of the problem.
"Roger Lee" <[email protected]> wrote:
>
Matthew,
Thanks for yor suggestions.
My classpath is set in the ANT.BAT & only points to the tools.jar, weblogic_sp.jar
& weblogic.jar.
I have my JARs in a manfest file in each directory with the "Class-Path:"
entry.
I have also added a new Bean with compiles & ejbcs fine. But I still
get an error
with my "createUser" method, saying the interface does not exist in the
bean class
or is not a public method.
I have even changed it's name to "createUserCandidate" just in case it
was clashing
with an existing method.
Any other ideas for investigation?
Thanks.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Roger Lee wrote:
The "warnings saying classes are being loaded from your classpath"are, I believe
just warning from Ant. I searched the newsgroups and it appears thatthis is not
a problem.These warnings are from ejbc. They are there to let you know that classes\interfaces
needed by your EJB are being loaded from your classpath and not your
jar. They
should be taken seriously. This could definitely be the cause of your
problem. As I
said in my previous posting, ejbc could be loading an old version of
your bean class
from your classpath. This old class may not contain the createUsermethod
with the
same signature as the method in your remote interface.
Is this an issue with WLS 6.1 sp2?I don't believe so.
I've wasted so much time on this any help would be appreciated.You essentially have three options.
1. Take my advice and make sure your classes are being loaded fromyour
jar and not
the classpath.
2. Post your entire jar so we can try to reproduce the problem.
3. Contact support.
- Matt
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Your bean and interface look fine. One thing you might try is explicitly
declaring
your createUser method to be public in your remote interface. I
don't
think this
will change the outcome but it's worth a try. When you run ejbcdo
you
get any
warnings saying classes are being loaded from your classpath ratherthan
your jar?
If this were the case, you could have an old copy of your bean inyour
classpath
that ejbc is picking up. If this doesn't help, I think the next
step
is to send me
or post your entire jar.
- Matt
Roger Lee wrote:
Typo that should have been "path", I had added "C:\bea\jdk131"
to
the
front of
my path & was getting the error.
Enclose my two classes in the attached file.
Thanks for you help.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Make sure you put C:\bea\jdk131 in front of your path (not classpath).
:) Assuming
this isn't the problem, can you please post any createUser method
declarations
in your
remote interface and the corresponding createUser methods in yourbean
class?
- Matt
Name: NOTiFY_&_NOTiFYBean.java
NOTiFY_&_NOTiFYBean.java Type: java/*
Encoding: base64

DB2 type 2 driver blocking WLS 8.1 SP2 on startup

Hi,
I use DB2 type 2 driver with WLS 8.1 SP2 and did configure a jdbc connection pool as described in edocs. But when I start the server and the server tries to deploy the jdbc connection pool, the server hangs. I took some thread dumps and the thread to load the driver seems to be stuck, as it always shows the same stack trace.
Did anybody manage to use this driver? Any suggestions?
Thanks,
Nicole
"Thread-1" id: 0x0x00000380 prio: 5 ACTIVE, NONDAEMON, GCABLE thread: 0x0xaf028500 lastj: 0x0xbfff8e74 at COM.ibm.db2.jdbc.app.DB2Driver.SQLAllocEnv(Native Method)@0xa026894e at COM.ibm.db2.jdbc.app.DB2Driver.<init>(Unknown Source)@0xa0268456 at java.lang.Class.newInstanceCached(Unknown Source)@0xa6e3e533 at weblogic.jdbc.common.internal.ConnectionEnvFactory.loadDriver(ConnectionEnvFactory.java:46)@0xa0e5e9d2 at weblogic.jdbc.common.internal.ConnectionEnvFactory.<init>(ConnectionEnvFactory.java:79)@0xa0e5e819 at weblogic.jdbc.common.internal.ConnectionPool.initPooledResourceFactory(ConnectionPool.java:514)@0xa0e5e298 at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:165)@0xa0e5d2d3 at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:880)@0xa0e59bf2 at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:133)@0xa0e59994 at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:291)@0xa0e58aa2 at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:178)@0xa0e58709 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)@0xa0e572a1 at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)@0xa0e56e36 at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)@0xa0e56649 at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)@0xa0e56424 at COM.jrockit.reflect.NativeMethodInvoker.invoke0(Native Method)@0xa6de9752 at COM.jrockit.reflect.NativeMethodInvoker.invoke(Unknown Source)@0xa6de987c at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Unknown Source)@0xa5d989f4 at java.lang.reflect.Method.invoke(Unknown Source)@0xa6de938d at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)@0xa4911d6c at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)@0xa491196d at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)@0xa4910de7 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)@0xa49109d7 at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)@0xa49103f4 at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)@0xa4910399 at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)@0xa4910276 at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)@0xa3623f4f at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)@0xa4d5d048 at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)@0xa0e56285 at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)@0xa0e5608e at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)@0xa0e55cca at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)@0xa0e55baa at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)@0xa177839b at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)@0xa1777f3e at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)@0xa6520534 at weblogic.Server.main(Server.java:32)@0xa65200a3 --- End of stack trace

Sorry, it is running now. There was a misspelling in the environment variable DB2INSTANCE and therefore the requested instance was not reachable. Still interesting, that this can even prevent the server from booting. Now that I corrected the variable in the environment, everything is fine.
Thanks,
Nicole

XMLSPY Special Edition for BEA WebLogic 8.1 and WLS 8.1 sp2

Hi,
I'm a newbie for WebLogic Server. I started with WLS 8.1 sp2 since I got the book "J2EE Applications and BEA WebLogic Server 2nd Edition" which was written for WLS 8.1.
While XMLSPY Special Edition for BEA WebLogic (version 5.4 something, built in 2003) is indeed packaged with WLS 8.1 sp2 and can be installed, but it'll pop up a window (ALTOVA License Manager) everytime when I try to use it. This window pops up because the license key is not installed during the installation and therefore can't be used unless a valid key is provided.
I wonder whether I really need to get XMLSPY Special Edition for BEA WebLogic 8.1 working in order to use WLS 8.1 just for the purpose of learning. If so, can someone share with me the the key-code for XMLSPY Special Edition for BEA WebLogic 8.1 please?
BTW, I tried to find something useful to this question/problem at ALTOVA website, no luck at all.
Thank you very much.
JF

Hi Ravi,
Thanks very much for your very helpful reply.
I got into the problem with xmlspy while I was trying to figure out why the WLS admin console missing the left pane/sidebar. There was only one non-expandable dot sign at the lefttop in the admin console. When I right-click on that little dot icon, the pulldown menu shows one option is to use XMLSPY to check (something along that line). Also, I see the XMLSPY button at the left bottom of my W2003 windows (just next to IE button). So, either way when I invoked XMLSPY I would get that pop up window which tells me there choices: type in a key-code, request for a trial key, or buy a license key. But eventually, I figured out the way to fix my problem - installing a newer version of j2sdk code. However, I wasn't sure whether the xmlspy issue would a hidden problem further down the road for me to learn WLS 8.1.
You're absoluately right commenting on the the right version of WLS to use at the beginning of learning WLS.
I have been VMWare Workstation for several months. I've created a CentOS 5.4 VM with WLS 11g installed. I played with with WLS 11g for a while and even followed through an Oracle online tutorial for that version. But I'm just used to learn something with a hard copy of book and I happen to have this old book on WLS 8.1 which seems to be highly rated before. I may continue to go through this book quickly if I can. However, if I experience too many hard problems down the road, I won't waste too much more time on this path. My long term goal is of course to learn more and better about WLS 11g and other Oracle related framework and tools. There is too much to learn. But the good thing is that Oracle provides everything free to learn. Also, I'm very encouraged by the quality of the Oracle tech group where I can turn for very useful help.
Thanks again and best regards,
JF

JAAS 1.0 with WLS 6.1 SP2 "Exception from LoginContext "

Similar Messages

Maybe you are looking for