Platform Domain and WorkShop JMS Control Problems

I created a platform domain and created a workflow in WLI. I would like to expose
the workflow from a web service. I successfully used the JMS control to send
the XML request into WLI and receive the reply from WLI. My problem is whenever
I try to execute the callback function when I receive my reply from JMS it his
a loop and never executes the callback to the client. In the same service i replaced
the JMS interaction with a timer and it works fine. The problem only occurrs when
the JMS control receives the reply and then invokes the callback. If I just receive
the reply without calling the callback everything works fine. Any ideas? Thanks

I did a little more debugging and it looks like when the message is sent to the
JMS Queue a different instance of the session EJB is calledback to when the JMS
reply is received. I noticed when my callback is invoked by JMS i have different
proxy and context objects. I hope this helps.
"David" <[email protected]> wrote:
>
I created a platform domain and created a workflow in WLI. I would like
to expose
the workflow from a web service. I successfully used the JMS control
to send
the XML request into WLI and receive the reply from WLI. My problem is
whenever
I try to execute the callback function when I receive my reply from JMS
it his
a loop and never executes the callback to the client. In the same service
i replaced
the JMS interaction with a timer and it works fine. The problem only
occurrs when
the JMS control receives the reply and then invokes the callback. If
I just receive
the reply without calling the callback everything works fine. Any ideas?
Thanks

Similar Messages

MPC800K usb and fan power control problem.

Hello all,
I own one of these MPC800K (K8M800 Via chipset...) boxes for one week now and since the first day I've always been surprised because both system and cpu fans were stuck to approx. 2100 rpm, whatever the cpu was doing. (Burning or not). It was a little noisy to my taste when just playing mp3 by exemple, so I tried yesterday to flash the mobo with what seemed to be the latest bios available. The board is reporting to be MS-7056, but when I browse MSI support pages, I can see that MPC800K is sometimes claimed to have 7056 or 6276 model motherboard. Confusing. When downloading bios, reference is made to 6276 mb on the download page, then inside the archive, bios file name is "A7056VMS.320". Even more confusing, but I made the choice to believe 7056 and 6276 are the same. (Can anyone confirm...?).
Flashing bios from one usb key ran perfectly, reboot ran perfectly, so did loading Windows (Home Edition). Oh, nice, it seemed to be my day of luck, because favor to this new bios (version 3.20, was running 3.13 before), cpu and system fans were now much more quiet when the cpu was not heavily loaded. Good. I love silence. Eh, but wait ! What the h... Where does come from this slight but really annoying hissing sound ? Seems to come from the inside of the box... You know, the kind of tipicaly electronical hissing sound, when some composant is subjet to some kind of stress. Then I noticed that the integrated card readers activity led was turned on but there wasn't even any card inserted. Abnormal. Trying to reboot. Ah, good. Led is now turned off. But there's still this annoying hissing sound, and... oh no, cpu and system fans are not quiet anymore, they went back to medium speed... Always.
Let's think. ... Let's try something. Shuting down windows, going to the bios, disabling USB integrated controler (because of the fancy behavior of the card readers led, obviously related to some kind of usb disorder, don't you think ?). Rebooting. Nice ! No more hissing sound, and fans control is now effective. Of course the bad news is that having disabled usb, I've no more usb ports working. Unfortunately, I need them.
Going back to the bios, re-enabling usb support, going back to windows, and playing with usb host controler in the device manager -> As soon as it is disabled, fan control is working perfectly. As soon as I re-enable it, automatic fan control is out of order again.
The choice is :
- functionnal USB ports but electronical hissing noises and no fan control
or
- fan control, no hissing noises, but no usb either.
Oh yes, I could always come back the old v3.13 bios. USB would be functionnal but I would lose automatic fan control and I would get rid of the hissing noises.
But :
1/ I would like to have fan control working !!!
2/ I did something I should not have done. (Guess what, I did not dump my old bios prior to flashing the new one, and there is absolutely no archive around the whole "googled" web.)
I also tried to install another version of windows to see how it would handle the situation. Well... I installed W2003 Server, and it's nearly the same mess : no fan control and hissing noise when usb enabled, but effective fan control and no more hissing noise when I disable "Standard enhanced PCI to USB Host Controler", and then a little surprise : usb ports are still working, but I lose 2.0 high speed, everything is falling to 1.1 full speed. (With XP Home, I had to disable VIA enhanced USB host controler, and then all usb support was off).
I think it's likely to be some kind of conflict between usb controler ressources and the way the mobo control the fans. Adress conflict, irq conflict ? I don't see how I could test since the bios doesn't let me change them in any way.
If someone has any idea to let me escape this bad situation, I would be *grateful*.
Maybe another release of the bios could help me ?

^
hmm, I have never hear of a USB controller making a hissing noise????
anyway try keeping usb controller enabled and disconnect the usb card reader. there should be a little cable that will enable you to disconnect the card reader. do you get a hissing noise with it disconnected?
eitherway I would think about return the system for another one. or warranty

Mule, Weblogic and MQ JMS : deadlock problem

Dear Oracle community,
We are hosting our Mule ESB (3.1) application on a Weblogic 10.3 (11g) server and are using IBM Websphere MQ's JMS solution (with libraries version 7.0.1.7).
The problem we are facing is that JMS connections are created by one of Weblogic's worker (thread) and the close() method for those connections are not necessarily called by the same thread.
This is bad because from what I know this behavior is undefined from JMS specification
(see http://docs.oracle.com/cd/E15051_01/wls/docs103/jms/design_best_practices.html#wp1061413 ) and it is a blocker issue in our case because this lead to a deadlock.
Do someone has any idea how to enforce the fact that the same thread do create and close the connection through Weblogic and/or Mule configuration (without re-implementing the connector) ?
Thanks in advance for your help,
Best regards,
Y.
PS : I've already posted this question on Mule ESB's forum : http://forum.mulesoft.org/mulesoft/topics/mule_weblogic_and_mq_jms_deadlock_problem
Edited by: user7428803 on May 14, 2012 2:26 PM

I hope you found a solution by now, but as an FYI:
* The JMS specification specifically requires that JMS providers support the ability to call connection.close() and session.close() from an arbitrary thread even when another thread is making calls on these objects. It furthermore goes into some detail about the expected behavior of these calls. The best practices link you cited alludes to this: "The JMS Specification states that multi-threading a session, producer, consumer, or message method results in undefined behavior +except when calling close().+"
* Depending on your use case, you may not need to use Mule to integrate MQ with WebLogic. WebLogic supports a variety of options for integrating MQ directly without the use of third party tooling. See http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm .
Tom

Choosing between Platform default and Other JMS Providers

Hi,
I'm new to JMS and trying to find what are scenarios when default J2EE platform JMS Provider is not enough and we need to go with other options like ActiveMQ. What extra services ActiveMQ provides that lacks in platform default provider.
thanks

I would rather say, evaluate your requirement against platform default(Server default) and ActiveMQ. If your default provider full fills the requirements; use the default one.

OS X Lion and Apple remote control problem

After installing OS X Lion my apple remote control no longer works properly. The menu wont come up on the screen, but it plays music if you press the buttons, but you are riding blind, can anyone help on this one?

It's not a problem with the remote, the problem is that Lion no longer has FrontRow.

Axis 700 - CPU Temp and Sys Fan Control Problems

I have just received an Axis 700 barebones. I ordered a 700 Lite with the fanless processor but I received a system with C7-D 1.5GHz processor and a system fan !. The heatsink looks the same as the Titan 700.
The BIOS and PC Alert report a CPU temp of 64C immediately on start-up rising to 70C at idle and 100C under heavy load. System temp is steady at aound 30C. I've measured the heatsink temp with thermometer and it's about half the value reported by PC Alert.
The system fan in the heatsink is running at full speed but BIOS and PC Alert reports 0 rpm. If I slow the fan almost to a stop with a piece of paper, I do get a fan speed of 1000-2000 rpm.
It feels like a BIOS problem but the MSI website only has a single version, v1.00. My board has version v1.1B4.
Does anybody have a similar experience?

It could be something wrong with the CPU FAN, else if you think that its BIOS issue you can ask MSI here: http://ocss.msi.com.tw/

Error encountered while trying to use EJB control in a Platform Domain

Hi,
I've configured a Weblogic Platform domain and installed all the application EJB's
thru a JAR file. When I try to access these EJB's from within Web Logic Workshop
using the EJB Control, I am able to find the Home and the Remote interfaces and
those boxes are populated correctly when I select the JNDI name from the Browse
button. But when I click on the "Create" button in EJB Control dialog box, I get
the following error
"The EJB Home interface selected in Step 3 cannot be loaded. The client interfaces
for the selected EJB must be present as individual classes in the WEB-INF\classes
directory of this project or the EJB's client JAR file must be present in the
WEB-INF\lib directory".
I copied my EJB Jar file to the WEB-INF\lib folder also. But still it gives the
same error message. Please let me know if I am missing something. Your help is
greatly appreciated.
Thanks
Vikram

Hi Pat,
I've restarted the complete Platform Domain Weblogic instance and it worked.
Thanks for your help.
Vikram
"Pat Bumpus" <[email protected]> wrote:
>
Hi,
I'm using a workshop domain from WebLogic Platform 7.0 SP1.
When you move the EJB classes (as a jar file) into the WEB-INF/lib directory,
then you need to redeploy the web application. In your last note you
mentioned
redeploying the EJB, but not the web app. Have you tried redeploying
the web
app, after you move the EJB jar file into WEB-INF/lib?
pat
"Vikram" <[email protected]> wrote:
Hi Pat,
Thanks for replying back immediately. I tried to redeploy the EJB and
copy the
client EJB classes to the WEB-INF\lib folder but still it doesn't work.
I've also
tried using some of the standard EJB's like "BEA_commerce.CategoryManager"
which
are part of the Platform domain and I am still getting the same error.
Are you working on a Weblogic Platform Domain or Weblogic workshop domain.
Just
wanted to confirm. Appreciate your help.
Thanks
Vikram
"Pat Bumpus" <[email protected]> wrote:
Hi,
After you copied the EJB into the WEB-INF/lib directory, did you redeploy
the
web application? I got a similar thing to work. Instead of movingthe
whole
EJB into WEB-INF/lib, I had ejbc create an EJB client jar and I moved
that into
my WEB-INF/lib directory. Then I redeployed the web application toload
the classes
and it worked.
pat
"Vikram" <[email protected]> wrote:
Hi,
I've configured a Weblogic Platform domain and installed all the application
EJB's
thru a JAR file. When I try to access these EJB's from within Web
Logic
Workshop
using the EJB Control, I am able to find the Home and the Remote interfaces
and
those boxes are populated correctly when I select the JNDI name from
the Browse
button. But when I click on the "Create" button in EJB Control dialog
box, I get
the following error
"The EJB Home interface selected in Step 3 cannot be loaded. The client
interfaces
for the selected EJB must be present as individual classes in theWEB-INF\classes
directory of this project or the EJB's client JAR file must be present
in the
WEB-INF\lib directory".
I copied my EJB Jar file to the WEB-INF\lib folder also. But stillit
gives the
same error message. Please let me know if I am missing something.
Your
help is
greatly appreciated.
Thanks
Vikram

Mqseries adapter on platform domain

I've got a problem with BEA WebLogic Adapter for MQSeries, release 7.0. I'm using
Platform Domain and when I try to test the adapter I get this kind of errors:
ERROR [MQService] WMQService: {4.2} NoClassDef exception processing agent XDMQEmitAgent:
com/ibm/mq/MQException
or
ERROR [manager] Can't create MQEvent MQ protocol: java.lang.NoClassDefFoundError:
com/ibm/mq/MQException. Possibly missing jar files.
So it seems that when I start the Platform server, even if the classpath is correctly
set, MQSeries files (e.g. com.ibm.mq.jar) are not loaded.. Also I couldn't find
specific information on how to add MQSeries adapter into this environment. In
the installation guide they only mention how to set up classpaths in wli domain
for adapter library into a file called "SetWliDomainData.cmd". But because I have
Platform Domain, I do not have that file at all and I've modified "startWeblogic.cmd"
file.
I really appreciate any help with this!
Regards, Anna

Given the lack of responses, I take the answer to be, "No, the MQSeries adapter can't read RFH2 headers." It also appears not to have the ability to use a selector like the JMS adapter. I will go back to using the JMS adapter to read from MQSeries queues, although it's changed enough since 10.1.2 that it's almost like using a different adapter as well.

Problems configuring Platform Domain with MS Sql Server

Hi,
We are having problems configuring a Platform Domain with MS Sql Server 2000.
We are using Weblogic version 7.0.0.2. These are the steps we followed
1.We manually created a database called TestDB and created a user account called
"system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
the TestDB created.
2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
in this file.
3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
and modified the RDBMS realm properties to point to the database.
4. ran the create_db script and it seemed to have run fine looking at the log
file.
5. I then tried to start the BEA Server instance and I get the following error.
I am also attaching the config.xml file for reference.
Appreciate any help/suggestions. Thanks in Advance.
Vikram
<Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
ating a database connection for the realm.
java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
193)
at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
02)
at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
69)
at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
elegate.java:962)
at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at weblogic.security.acl.Realm.getRealm(Realm.java:87)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
<Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
in
itialize the server: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
[config.xml]

Try removing the server section from the SchemaProperties line.
Preferrably do not use localhost or hostnames in the server
configuration file.
<RDBMSRealm
Name="wlcsRealm"
DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
DatabasePassword="weblogic"
DatabaseURL="jdbc:weblogic:mssqlserver4:yourIPAddress:1433"
RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"
SchemaProperties="user=system;password=weblogic"/>
Also consider ...
If you have a new Portal database created in SQL Server?
Does the user system have the Portal database as his default database?
-- Jim
Vikram wrote:
Hi,
We are having problems configuring a Platform Domain with MS Sql Server 2000.
We are using Weblogic version 7.0.0.2. These are the steps we followed
1.We manually created a database called TestDB and created a user account called
"system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
the TestDB created.
2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
in this file.
3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
and modified the RDBMS realm properties to point to the database.
4. ran the create_db script and it seemed to have run fine looking at the log
file.
5. I then tried to start the BEA Server instance and I get the following error.
I am also attaching the config.xml file for reference.
Appreciate any help/suggestions. Thanks in Advance.
Vikram
<Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
ating a database connection for the realm.
java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
193)
at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
02)
at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
69)
at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
elegate.java:962)
at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at weblogic.security.acl.Realm.getRealm(Realm.java:87)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
in
itialize the server: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Domain Name="epmsDomain">
<Log
FileName="logs/wl-domain.log"
Name="epmsDomain"
/>

<Server
Name="platformServer"
     ListenAddress="localhost"
ListenPort="7501"
NativeIOEnabled="true"
TransactionLogFilePrefix="logs/"
>
<SSL
Name="platformServer"
ListenPort="7502"
Enabled="true"
ServerCertificateChainFileName="ca.pem"
ServerCertificateFileName="democert.pem"
ServerKeyFileName="demokey.pem"
/>
<Log
FileName="logs/weblogic.log"
/>
<WebServer
DefaultWebApp="splashPage"
LogFileName="./logs/access.log"
LoggingEnabled="true"
Name="platformServer"
/>
</Server>

<JDBCConnectionPool
Name="commercePool"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
URL="jdbc:weblogic:mssqlserver4:localhost:1433"
Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Password="weblogic"
InitialCapacity="20"
MaxCapacity="20"
CapacityIncrement="1"
RefreshMinutes="0"
ShrinkingEnabled="false"
Targets="platformServer"
TestConnectionsOnReserve="false"
TestTableName="WEBLOGIC_IS_ALIVE"
/>

<JDBCConnectionPool
CapacityIncrement="2"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
InitialCapacity="8"
LoginDelaySeconds="1"
MaxCapacity="36"
Name="wliPool"
Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Password="weblogic"
RefreshMinutes="0"
ShrinkPeriodMinutes="15"
ShrinkingEnabled="true"
Targets="platformServer"
URL="jdbc:weblogic:mssqlserver4:localhost:1433"
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="platformServer"
/>
<JDBCDataSource
JNDIName="weblogic.jdbc.pool.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="platformServer"
/>
<JDBCDataSource
JNDIName="WLAI_DataSource"
Name="WLAI_DataSource"
PoolName="wliPool"
Targets="platformServer"
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="true"
JNDIName="com.bea.wlpi.TXDataSource"
Name="TXDataSource"
PoolName="wliPool"
Targets="platformServer"
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="true"
JNDIName="WLCHub.DS"
Name="WLCHub.DS"
PoolName="wliPool"
Targets="platformServer"/>
/>

<JDBCTxDataSource
     EnableTwoPhaseCommit="true"
JNDIName="cgDataSource"
Name="cgDataSource"
PoolName="commercePool"
Targets="platformServer"/>
<JDBCTxDataSource
EnableTwoPhaseCommit="true"
JNDIName="cgSampleDataSource"
Name="cgSampleDataSource"
PoolName="commercePool"
Targets="platformServer"/>
<JMSConnectionFactory JNDIName="weblogic.jws.jms.QueueConnectionFactory"
Name="cgQueue" Targets="platformServer"/>
<JMSJDBCStore ConnectionPool="commercePool" Name="cgJDBCStore" PrefixName="WEBLOGIC"/>
<JMSServer Name="cgJMSServer" Store="cgJDBCStore" Targets="platformServer">
<JMSQueue JNDIName="jws.queue" Name="cgJWSQueue" StoreEnabled="default"/>
</JMSServer>
<JTA Name="epmsDomain" TimeoutSeconds="3600"/>


<JDBCConnectionPool
Name="dataSyncPool"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
URL="jdbc:weblogic:mssqlserver4:localhost:1433"
Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Password="WEBLOGIC"
InitialCapacity="1"
MaxCapacity="5"
CapacityIncrement="1"
RefreshMinutes="0"
ShrinkingEnabled="false"
TestConnectionsOnReserve="false"
TestTableName="WEBLOGIC_IS_ALIVE"
Targets="platformServer"/>
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.dataSyncPool"
Name="dataSyncPool"
PoolName="dataSyncPool"
Targets="platformServer"/>
/>

<Security
GuestDisabled="false"
Name="epmsDomain"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm"
CompatibilityMode="true"
/>
<PasswordPolicy
Name="wl_default_password_policy"
/>
<Realm
Name="wl_default_realm"
CachingRealm="wlcsCachingRealm"
FileRealm="wl_default_file_realm"
/>
<CachingRealm
BasicRealm="wlcsRealm"
CacheCaseSensitive="true"
Name="wlcsCachingRealm"
/>
<RDBMSRealm DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
DatabasePassword="weblogic"
DatabaseURL="jdbc:weblogic:mssqlserver4:localhost:1433"
SchemaProperties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Name="wlcsRealm"
RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"/>
<FileRealm
Name="wl_default_file_realm"
/>
<StartupClass
ClassName="com.beasys.commerce.ebusiness.security.KeyBootstrap"
FailureIsFatal="false"
Name="KeyBootstrap"
Targets="platformServer"
/>

<JMSConnectionFactory Name="WLI_B2B_TopicFactory"
JNDIName="com.bea.wli.b2b.server.TopicConnectionFactory"
AllowCloseInOnMessage="true"
UserTransactionsEnabled="true"
Targets="platformServer"
/>
<JMSConnectionFactory
AllowCloseInOnMessage="true"
JNDIName="com.bea.wli.b2b.rosettanet.QueueConnectionFactory"
Name="RNQueueFactory"
Targets="platformServer"
UserTransactionsEnabled="true"
/>
<JMSConnectionFactory
AllowCloseInOnMessage="false"
DefaultDeliveryMode="Persistent"
DefaultPriority="4"
DefaultTimeToLive="0"
JNDIName="com.bea.wlai.JMSConnectionFactory"
MessagesMaximum="10"
Name="WLAI_JMSConnectionFactory"
OverrunPolicy="KeepOld"
UserTransactionsEnabled="true"
Targets="platformServer"/>
/>
<JMSConnectionFactory
AllowCloseInOnMessage="true"
JNDIName="com.bea.wlpi.TopicConnectionFactory"
Name="wlpiFactory"
Targets="platformServer"
UserTransactionsEnabled="true"
/>
<JMSConnectionFactory
AllowCloseInOnMessage="true"
JNDIName="com.bea.wlpi.QueueConnectionFactory"
Name="wlpiQueueFactory"
Targets="platformServer"
UserTransactionsEnabled="true"
/>
<JMSJDBCStore
ConnectionPool="wliPool"
Name="JMSWLIStore"
PrefixName="PBPUBLIC"
/>
<JMSServer Name="WLIJMSServer"
Targets="platformServer"
TemporaryTemplate="TemporaryTemplate"
Store="JMSWLIStore">
<JMSTemplate Name="TemporaryTemplate"/>

<JMSQueue Name="WLI_B2B_RNEncoderQueue"
JNDIName="com.bea.wli.b2b.rosettanet.EncoderQueue"/>
<JMSTopic Name="WLI_B2B_Topic"
JNDIName="com.bea.wli.b2b.server.B2BTopic"/>
<JMSQueue Name="WLI_B2B_OutboundQueue"
JNDIName="com.bea.b2b.OutboundQueue"/>

<JMSTopic Name="wlpiEvent"
JNDIName="com.bea.wlpi.EventTopic"/>
<JMSQueue Name="WLI_BPM_Timer"
JNDIName="com.bea.wli.bpm.TimerQueue"
StoreEnabled="true"
Template="WLI_JMSTemplate"/>
<JMSQueue Name="WLI_BPM_Event"
JNDIName="com.bea.wli.bpm.EventQueue"
StoreEnabled="true"
Template="WLI_JMSTemplate"/>
<JMSQueue Name="WLI_BPM_ValidatingEvent"
JNDIName="com.bea.wli.bpm.ValidatingEventQueue"
StoreEnabled="true"
Template="WLI_JMSTemplate"/>
<JMSTopic Name="WLI_BPM_Error"
JNDIName="com.bea.wli.bpm.ErrorTopic"/>
<JMSTopic Name="WLI_BPM_Audit"
JNDIName="com.bea.wli.bpm.AuditTopic"/>
<JMSTopic Name="WLI_BPM_Notify"
JNDIName="com.bea.wli.bpm.NotifyTopic"/>

<JMSQueue Name="WLAI_ASYNC_REQUEST_QUEUE"
JNDIName="com.bea.wlai.ASYNC_REQUEST_QUEUE"/>
<JMSQueue Name="WLAI_ASYNC_RESPONSE_QUEUE"
JNDIName="com.bea.wlai.ASYNC_RESPONSE_QUEUE"/>
<JMSQueue Name="WLAI_EVENT_QUEUE"
JNDIName="com.bea.wlai.EVENT_QUEUE"/>
<JMSTopic Name="WLAI_EVENT_TOPIC"
JNDIName="com.bea.wlai.EVENT_TOPIC"/>
     
     <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_ASYNC_RESPONSE_QUEUE" Name="WLAI_WORKSHOP_ASYNC_RESPONSE_QUEUE"/>
     <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_EVENT_QUEUE" Name="WLAI_WORKSHOP_EVENT_QUEUE"/>

<JMSQueue Name="WLI_FailedEvent"
JNDIName="com.bea.wli.FailedEventQueue"
StoreEnabled="true"/>
<JMSTemplate Name="WLI_JMSTemplate"
ErrorDestination="WLI_FailedEvent"
RedeliveryDelayOverride="60000"
RedeliveryLimit="10"/>
</JMSServer>
<JMSJDBCStore Name="JMSWLIStore"
ConnectionPool="wliPool"
PrefixName="platformServer"/>






<Application
Deployed="true"
Name="taxWSApp"
Path="C:/bea/user_projects/epmsDomain/beaApps/taxWSApp"
TwoPhase="true"
>
<EJBComponent
Name="tax"
URI="tax.jar"
Targets="platformServer"
/>
<WebAppComponent
Name="tax-webservice"
URI="tax-ws"
Targets="platformServer"
/>
</Application>
<Application
Deployed="true"
Name="paymentWSApp"
Path="C:/bea/user_projects/epmsDomain/beaApps/paymentWSApp"
TwoPhase="true"
>
<EJBComponent
Name="payment"
URI="payment.jar"
Targets="platformServer"
/>
<WebAppComponent
Name="payment-edit webservice"
URI="pay-ws"
Targets="platformServer"
/>
</Application>

<Application
Deployed="true"
Name="wlpDocsApp"
Notes=""
Path="C:/bea/weblogic700/portal/lib"
TwoPhase="true"
>
<WebAppComponent
IndexDirectoryEnabled="false"
Name="wlpDocs"
Targets="platformServer"
URI="wlpDocs.war"
ServletReloadCheckSecs="300"
/>
</Application>

<Application
Deployed="true"
Name="portalApp"
Notes=""
Path="C:/bea/user_projects/epmsDomain/beaApps/portalApp"
TwoPhase="true"
>
<ApplicationConfiguration
Name="portalApp"
Targets="platformServer"
URI="META-INF/application-config.xml"
/>
<EJBComponent
Name="events"
Targets="platformServer"
URI="events.jar"
/>
<EJBComponent
Name="pipeline"
Targets="platformServer"
URI="pipeline.jar"
/>
<EJBComponent
Name="property"
Targets="platformServer"
URI="property.jar"
/>
<EJBComponent
Name="rules"
Targets="platformServer"
URI="rules.jar"
/>
<EJBComponent
Name="usermgmt"
Targets="platformServer"
URI="usermgmt.jar"
/>
<EJBComponent
Name="customer"
Targets="platformServer"
URI="customer.jar"
/>
<EJBComponent
Name="ebusiness"
Targets="platformServer"
URI="ebusiness.jar"
/>
<EJBComponent
Name="portal"
Targets="platformServer"
URI="portal.jar"
/>
<EJBComponent
Name="campaign"
Targets="platformServer"
URI="campaign.jar"
/>
<EJBComponent
Name="catalogws"
Targets="platformServer"
URI="catalogws.jar"
/>
<EJBComponent
Name="document"
Targets="platformServer"
URI="document.jar"
/>
<EJBComponent
Name="ejbadvisor"
Targets="platformServer"
URI="ejbadvisor.jar"
/>
<EJBComponent
Name="mail"
Targets="platformServer"
URI="mail.jar"
/>
<EJBComponent
Name="placeholder"
Targets="platformServer"
URI="placeholder.jar"
/>
<WebAppComponent
Name="toolSupport"
Targets="platformServer"
URI="toolSupport"
ServletReloadCheckSecs="300"
/>
<WebAppComponent
Name="tools"
Targets="platformServer"
URI="tools"
ServletReloadCheckSecs="300"
/>
<WebAppComponent
Name="datasync"
Targets="platformServer"
URI="datasync"
ServletReloadCheckSecs="300"
/>
<WebAppComponent
Name="splashPage"
Targets="platformServer"
URI="splashPage"
ServletReloadCheckSecs="300"
/>

</Application>
<Application
Deployed="true"
TwoPhase="true"
StagedTargets="platformServer"
Name="p13nConsoleApp"
Path="C:/bea/weblogic700/portal/lib"
>
<WebAppComponent
Name="p13nConsole"
ServletReloadCheckSecs="300"
Targets="platformServer"
URI="p13nConsole.war"
/>
</Application>

<Application Deployed="true" LoadOrder="900" Name="EAI" Path="C:/bea/weblogic700/samples/workshop/wlai/ear/" TwoPhase="true">
<EJBComponent
DeploymentOrder="100"
Name="repository-ejb.jar"
     Targets="platformServer"
URI="repository-ejb.jar"/>
<EJBComponent Name="WLI-B2B Startup"
DeploymentOrder="200"
Targets="platformServer"
URI="b2b-startup.jar"/>
<EJBComponent DeploymentOrder="300" Name="b2b-rosettanet.jar" Targets="platformServer" URI="b2b-rosettanet.jar"/>
<WebAppComponent DeploymentOrder="400" Name="b2b.war" Targets="platformServer" URI="b2b.war"/>
<WebAppComponent DeploymentOrder="500" Name="b2bconsole.war" Targets="platformServer" URI="b2bconsole.war"/>
<EJBComponent DeploymentOrder="600" Name="WLI-AI Server" Targets="platformServer" URI="wlai-server-ejb.jar"/>
<WebAppComponent DeploymentOrder="700" Name="wlai" Targets="platformServer" URI="wlai.war"/>
<EJBComponent DeploymentOrder="800" Name="WLI-AI Async Processor" Targets="platformServer" URI="wlai-asyncprocessor-ejb.jar"/>
<EJBComponent DeploymentOrder="900" Name="WLI-AI Event Processor" Targets="platformServer" URI="wlai-eventprocessor-ejb.jar"/>
<EJBComponent DeploymentOrder="1000" Name="wlpi-ejb.jar" Targets="platformServer" URI="wlpi-ejb.jar"/>
<EJBComponent DeploymentOrder="1100" Name="wlpi-master-ejb.jar" Targets="platformServer" URI="wlpi-master-ejb.jar"/>
<EJBComponent DeploymentOrder="1200" Name="wlpi-mdb-ejb.jar" Targets="platformServer" URI="wlpi-mdb-ejb.jar"/>
<EJBComponent DeploymentOrder="1300" Name="WLXTEJB.jar" Targets="platformServer" URI="WLXTEJB.jar"/>

Problem with logical domain and boot net

Trying to install a new domain on a T2000. Able to get to "Configuring devices" but then it just sits and twirls... What have I configured wrong in the domain creation?
I have:
{0} ok show-devs
/cpu@7
/cpu@6
/cpu@5
/cpu@4
/cpu@3
/cpu@2
/cpu@1
/cpu@0
/virtual-devices@100
/virtual-memory
/memory@m0,8000000
/aliases
/options
/openprom
/chosen
/packages
-virtual-devices@100/channel-devices@200
\virtual-devices@100/console@1
/virtual-devices@100/ncp@4
/virtual-devices@100/channel-devices@200/disk@0
/virtual-devices@100/channel-devices@200/network@0
/openprom/client-services
/packages/obp-tftp
/packages/kbd-translator
/packages/SUNW,asr
/packages/dropins
/packages/terminal-emulator
/packages/disk-label
/packages/deblocker
/packages/SUNW,builtin-drivers
|0} ok show-disks
/) /virtual-devices@100/channel-devices@200/disk@0

There are a number of issues with network booting in LDOM 1.0.2, I think they affect all versions of the LDOM software though. If you add a vnet to a guest domain and then try and jumpstart a guest domain from time to time immediately after the guest domain does the RARP request it hangs. Just sending a break to the guest domain, going back to the ok prompt and starting the boot net - install again generally fixes it.
Also there are some gotcha's with LDOM's that affect jumpstart.
1) If you chose option a) harden the OS using JASS when doing the installation of the LDOM software and you have the jumpstart server on the control domain then it isn't going to work. JASS turns off things like rpcbind which will prevent jumpstart from working. The same problem affects network booting. You would think that running a jass-execute -u to undo the hardening of the o/s in the control domain would work but it doesn't and you have to start over with a fresh solaris image for the control domain. This only applies if you have your jumpstart server on your control domain.
2) Since jumpstart relies on the MAC of the client to function and since with LDOM's the MAC is dynamically assigned from a pool of address's you can end up with the wrong entry in /etc/ethers on your jumpstart server. That is worth checking.
3) Since the MAC of the virtual network device isn't the same as the MAC shown when you run banner at the ok prompt in the guest domain you can end up with the wrong entry in /etc/ethers. Either do a boot net (vnet1 whatever) and then make a note of the MAC its broadcasting or do an ldm list-bindings domainname for the guest you want to network boot and copy and paste the MAC of the virtual network you are going to be booting from.
All the regular gotcha's with net boot and jumpstart still apply with LDOM's but so do all the usual fixes. Use of snoop will allow you do debug most problems. Also using show-nets at the ok prompt in the guest domain and make sure that you have the right number of virtual networks.
Paul.

My problem is that after printing the first photo or picture, when I come to print a second, both the Colour Management and Epson Colour Controls are greyed out and showing No Colour Management

I have recently purchased a Mac computer (updated to Maverick) to go with my Epson Stylus Photo RX500 printer which has given excellent service with my old Windows computer. However, when trying to print pictures or photos via Photoshop Elements 11, the best results I can get are using the Colour Management and Epson Colour controls in the printing options box.
My problem is that after printing the first photo or picture, when I come to print a second, both the Colour Management and Epson Colour Controls are greyed out and showing No Colour Management, The only way I can reset the controls is to shut down the printer and computer and restart.
Could there may be a setting somewhere that I need to adjust please? I have been in touch with Epson and they say that the Epson Colour controls are part of the Photoshop Elements software but a post on the Adobe forum brought no results and I am unable to contact Adobe.
<Edited by Host>

Hello Garry. Thanks for the reply. I guess I should have used a different title from "How do I post a question?" That should come after trying to resolved the colour settings first. However, to answer your question, after experimenting with all the different settings in Photoshop Elements and Epson software, I now start with PSE11 Colour settings then click "no colour management" then after clicking Print, I choose "More Options/Colour Management/Colour Handling/Printer Manages Colour" then I choose "Page Setup/Layout/Colour Matching" which then shows Epson Colour Controls but I also choose "Layout/Colour Management" which then shows "Colour Controls/Mode" I then of course choose an Epson printer profile depending on the paper I am using. I get good results but as I said, the Colour Matching and Colour Controls are then greyed out. Hope that makes sense.

CS6 problem. When I open the Mask panel, it takes up the entire screen width and the Looks controls disappear, Also, there is a new panel below the Mask panel that seems to have no purpose that I can find. The documentation says "Mask and Look panels - Th

CS6 problem. When I open the Mask panel, it takes up the entire screen width and the Looks controls disappear, Also, there is a new panel below the Mask panel that seems to have no purpose that I can find. The documentation says "Mask and Look panels - The Mask panel is now placed next to the Look panel. WIth the masking and grading tools placed side-by-side, you can now work faster on the mask workflow." Is there a way to move, hide, or otherwise manipulate the panels for a custom layout? All the examples I can find on the Web show the Looks panel to the left of the Mask panel where the controls are available.

Ok, here is what I have so far. Appdelete the iWork and reinstalled. Pages and Number work, but not Keynote.
Now, I downloaded a couple apps that I need, and no matter what I did, the spinning ball came up and the download stopped till it unlocked itself. It is really frustrating because the download was not completed and whatever came through would not mount. Could this issue be the internet connection? Permission fix showed a lot of Airport issues. I will try to run permissions fix again.

JDBC, JMS and EJB transactions - possible problem?

Hello,
          I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
          XDoclet.
          In my current project I have the following piece of code
          in one of my message driven beans (code cited as pseudocode
          without unnecessary details):
          * @ejb.bean name="MyMessageProcessor"
          * display-name="Display name for a MyMessageProcessor"
          * jndi-name="ejb/MyMessageProcessor"
          * description="Bean MyMessageProcessor"
          * destination-type="javax.jms.Queue"
          * transaction-type="Container"
          * acknowledge-mode="Auto-acknowledge"
          * subscription-durability="Durable"
          * generate="false"
          * @ejb.transaction type="Required"
          public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
          public void onMessage(Message msg) {
               try {
                    //obtaining connections to two different databases via JNDi
                    java.sql.Connection connOne =
                    ((DataSource)ctx.lookup("DataSourceOne")).getConnection();
                    java.sql.Connection connTwo =
                         ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                    // performing some UPDATEs and INSERTs on connOne and connTwo
                    // calling some other methods of this bean
                    //creating the reply JMS message and sending it to another JMS queue
                    Message msgTwo = this.createReplyMessage(msg)
                    this.queueSender.send(msgTwo);
                    //commiting everything
                    this.queueSession.commit();
               } catch (Exception ex) {
               try {
                    if (this.queueSession!=null) this.queueSession.rollback();
               } catch (JMSException JMSEx) {};
               this.context.setRollbackOnly();
          Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
          connection pool with non-XA jdbc driver. Everything worked fine
          including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
          to database and the incomming message was thrown back to the my bean's
          queue).
          When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
          participate in a global transaction. When I changed both datasources
          to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
          EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
          and the JMS message wasn't resent to the JMS queue.
          So here are my questions:
               1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
               Are there any global server configurations, which may influence this situation?
               2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
               (of course, if necessary)?
               3. Are there any JMS Queue settings, which would disable the container to send message back to the
               queue in case of setRollbackOnly()? How should be the Queue configurated?
          As I am new to the topic and the deadline for the project seems to be too close I would be grateful
          for any help.
          This message was sent to EJB list and JDBC list.
          Sincerely yours,
          Marcin Zakidalski

Hi,
          I found these information extremely useful and helpful.
          The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
          Anyway, I still have some problems. I have made some changes to the
          code cited in my previous mail. These changes included changing QueueSessions
          to non-transactional. I also set the "Honorate global transactions" to true.
          I am using XA JDBC driver. After setting "Enable local transactions" to false
          (I did it, because I assume that JDBC transactions should be part on the global
          EJB transaction) I got the following error:
          java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
          driver supports performing SQL operations with no global transaction, explicitly allow it by setting
          "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
          transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
          complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
          I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
          the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
          My questions are as follows:
          1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
          thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
          from doing that? Can using setAutocommit(true/false) change the situation for better?
          2. How to encourage the JDBC driver to be a part of EJB transaction?
          3. As I have noticed each of ejb method has its own transactions (transactions have different
          Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
          way that if already started transaction exists it is used by the called method?
          4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
          impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
          enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
          solved programmically?
          Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
          I am loosing the ability to perform all actions in one transaction.
          Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
          Marcin

"Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run se

Team,
I am trying to Install Exchange on my Lab, getting below error
message.
The Schema Role is installed on Root Domain and trying to install
exchange on Child domain.
1 Root Domain - 1 Child domain. both are located on single site.
“Setup encountered a problem while validating
the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run setup with the /prepareAD parameter and wait for
replication to complete.”
Followed below articles:
http://support.risualblogs.com/blog/2012/02/21/exchange-2010-sp2-upgrade-issue-exchange-organization-level-objects-have-not-been-created-and-setup-cannot-create-them-because-the-local-computer-is-not-in-the-same-domain-and-site-as-the-sche/
http://www.petenetlive.com/KB/Article/0000793.htm
transferred the schema roles to different server on root domain, still no luck.
can someone please help me.
regards
Srinivasa k
Srinivasa K

Hi Srinivasa,
I guess, you didn't completed the initial setup schemaprep and adprep before starting the installation. You can do it as follows:
1. Open command Prompt as administrator and browse to the root of installation cd and run Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
After finishing this,
2. Setup.exe /PrepareAD /OrganizationName:"<organization name>" /IAcceptExchangeServerLicenseTerms
3. To prepare all domains within the forest run Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms. If you want to prepare a specific domain run Setup.exe /PrepareDomain:<FQDN of the domain you want to prepare> /IAcceptExchangeServerLicenseTerms
4. Once you complete all of the 3 steps, install the pre-requisities for Exchange 2013
5. Finally, run the setup program
Hope this will help you
Regards from Visit ExchangeOnline |
Visit WindowsAdmin

I cant login to ituines and my icloud control panel won't open on Windows 7 in Ireland and I'ma system builder so NO its not a problem with my machine!

I cant login to ituines and my icloud control panel won't open on Windows 7
In Ireland
and NO its not a system problem - something is wrong with the icloud servers and I'd like some feedback

I would try completly removing all the itunes associated programs and reinstalling under a new user
http://support.apple.com/kb/ht1923
(note that the order they are uninstalled in in step1 is important as is verifying they are completely removed step2)

Platform Domain and WorkShop JMS Control Problems

Similar Messages

Maybe you are looking for