Glassfish vs weblogic

hello everybody,
i dont know if similar posts were posted before.. if so, i am sorry for your time. as a minor research project, i was assigned to search weblogic and glassfish and compare them according to the parameters such as prices, required minimum hardware configuration, maximum load and etc.
is there anyone who can help me with this? maybe there is a specific site indicating these above mentioned parameters?
another thing that i wonder is, since glassfish is free (i mean os) and weblogic is expensive (heard that it is $10.000 for each computer but not sure about that), why someone should choose wl over gf?
i mean is there a really performace difference between these two that someone agrees to pay 10 times more? is the quality 10 times worse in gf?
i have been searching for a comparison (in terms of price, performance and load capacity) of these two app-servers; however, i couldnt find nothing but the obsolete posts.
if anyone can help me, it would be a great help to me.. thanks to all again,
- ismet

>
can i ask you 2 more questions..Sure, my pleasure.
considering the price, performance and maximum load parameters, what is the threshold for you to select GF over WL?
price always matters but then we have also to see the scalability and robustness of the product and its future. I have found the performance of WLS slightly better than GF, and same goes for the concurrent users. I have used both with more than 500-800 concurrent users and WLS performed slightly better and it was easier to manage, and load balancing just rocks.
do you also know the maximum loads of the servers (i mean, how many total user can connect to each server at the same time?)
There is no single limit when you implement load balancing and clustering. The more power and scalability you get, when you add more nodes.
regards
>
thanks again for your time,
BR,
- ismet

Similar Messages

Migrating from Glassfish to Weblogic

Hello,
We have a java project (EJB 3) that we deploy in glassfish. With new changes to company's infrastructure, glassfish is not available and I need to deploy the EAR files to Weblogic 10.3.0. We build the ear file using maven and get any required dependencies, however as expected, I have started running into issues. I have a stacktrace below here but does anyone have a suggestion for me as to how to get this done?
Unable to access the selected application.
Exception in AppMerge flows' progression
Exception in AppMerge flows' progression
[J2EE:160161]Error while parsing the Application descriptors for mi-connector.ear: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND problem: cvc-attribute.4: The value '6' does not equal the fixed value '5' of attribute 'version':<null> at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234) at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221) at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146) at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306) at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788) at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768) at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311) at weblogic.application.compiler.CompilerCtx.setApplicationDescriptor(CompilerCtx.java:138) at weblogic.application.compiler.AppcUtils.setDDs(AppcUtils.java:142) at weblogic.application.compiler.flow.DescriptorParsingFlow.compile(DescriptorParsingFlow.java:57) at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36) at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96) at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49) at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94) at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47) at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36) at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96) at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157) at weblogic.utils.compiler.Tool.run(Tool.java:158) at weblogic.utils.compiler.Tool.run(Tool.java:115) at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169) at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88) at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63) at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181) at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:156) at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:661) at com.bea.console.actions.app.install.Flow$2.execute(Flow.java:463) at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:4625) at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:461) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:255) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106) at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:54) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) .

You are trying to deploy a Java EE 6 application to a Java EE 5 Application Server.
Weblogic is still not a certified Java EE 6 Application Server.
http://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Edition#Java_EE_6_certified
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question.

Calling an ejb from glassfish to weblogic server

I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
Basically what I've attempted is this:
1.) I add these jvm properties to the glassfish startup:
-Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
-Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
-Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
...glassfish won't start then because of the weblogic.jar...
3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
Now I try it and get:
(I'm skipping some of the stacktrace at the start)
.....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
Am I going down the wrong path?
I've also tried these other proposed solutions:
1.) Changing the connection properties of the InitialContext to use these properties:
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "weblogic");
2.) Using RMI over IIOP instead of T3.
None of these with any luck.
If anyone has done this successfully I'd appreciate some insight.
Regards,
Eric

I'd like to be able to call a stateless session bean from a glassfishV3 server that is residing on weblogic 9.2.3. (Ejb spec 2.1 NOT 3.0 please)
I've done this successfully from Tomcat to weblogic, but there are a few hiccups when trying this on glassfish.
Basically what I've attempted is this:
1.) I add these jvm properties to the glassfish startup:
-Dorg.omg.CORBA.ORBClass=weblogic.corba.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=weblogic.corba.orb.ORB
-Djavax.rmi.CORBA.PortableRemoteObjectClass=weblogic.iiop.PortableRemoteObjectDelegateImpl
-Djavax.rmi.CORBA.UtilClass=weblogic.iiop.UtilDelegateImpl
2.) Copy weblogic.jar, tools.jar, and webservices.jar from the weblogic/server/lib directory to the glassfish lib/ext directory
...glassfish won't start then because of the weblogic.jar...
3.) Move the weblogic.jar to the WEB-INF/lib directory of my war in glassfish.
Now I try it and get:
(I'm skipping some of the stacktrace at the start)
.....java.lang.IllegalAccessError: tried to access method weblogic.kernel.KernelStatus.initialized()V from class weblogic.kernel.Kernel at weblogic.kernel.Kernel.ensureInitialized......
I'm guessing that this has to do with the "weblogic kernel" not being initialized. So now I'm stuck.
Am I going down the wrong path?
I've also tried these other proposed solutions:
1.) Changing the connection properties of the InitialContext to use these properties:
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://localhost:7001");
env.put(Context.SECURITY_PRINCIPAL, "weblogic");
env.put(Context.SECURITY_CREDENTIALS, "weblogic");
2.) Using RMI over IIOP instead of T3.
None of these with any luck.
If anyone has done this successfully I'd appreciate some insight.
Regards,
Eric

Weblogic Eclipselink Sequence Table Connection Pool Sequence Separate transaction while JTA on main transaction

Hi,
And thanks in advance for your support.
In weblogic 12, managing to get the eclipse link connection sequencing mechanism when one uses Tables for sequencing entity ids seems to be complicated.
QUICK REFERENCE:
http://www.eclipse.org/eclipselink/api/2.5/org/eclipse/persistence/config/PersistenceUnitProperties.html
The concept:
While having EJB, MDBs etc... run on a JEE container, be it glassfish or weblogic, it should be possible to have the main thread transaction be managed as part of JTA global transactions by the contianer.
Namely, pumping messages to JMS queues, persisting entities etc.
Meanwhile, it should be also possible to as the transaction is on going write and update entity ids from sequencing tables.
For this very purpose, eclipse link provides persistence.xml properties, such as the now deprecated eclipselink.jdbc.sequence-connection-pool" value="true", to fullfill this very purpose.
This option greatly avoids dead longs, by allowing eclipse link to fetch a non JTA managed connection, pseudo "two phase locking read table update table" go to the datbase and fetch a new sequence.
The same mechnism under JTA is a disaster. A transaction that creates ten different entities, might do ten reads and updates on this table, while mean while a competing transaction might be trying to do the same. It is guaranteed dead lock with minimal stress on the environment.
Under glassfish, for example, tagging a persistence.xml with :
<persistence-unit name="MY_PU" transaction-type="JTA">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/DERBY_DS</jta-data-source>
        <non-jta-data-source>jdbc/DERBY_DS</non-jta-data-source>
        <properties>
            <property name="eclipselink.jdbc.sequence-connection-pool" value="true" />
        </properties>
</peristence-unit>
does miracles, when entities are using TABLE sequencing.
Under weblogic, say you are using the Derby embedded XA driver with two phase commit, deploying the applicaiton immediately leads to:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Cannot call commit when using distributed transactions
Error Code: 0
at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicCommitTransaction(DatabaseAccessor.java:426)
at org.eclipse.persistence.internal.databaseaccess.DatasourceAccessor.commitTransaction(DatasourceAccessor.java:389)
at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.commitTransaction(DatabaseAccessor.java:409)
at org.eclipse.persistence.internal.sequencing.SequencingManager$Preallocation_Transaction_Accessor_State.getNextValue(SequencingManager.java:579)
at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067)
at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70)
at org.eclipse.persi
While weblogic is right that their might be a distributed transaction ongoing, it is mistaken in the fact tha tthe connection requested by eclipse link for generating the ID should be part of the global transaciton.
Eclipse link provides other ways to attempt to configure the sequencing mechanism, by sating for example a non-jta transaction.
I have attempted also using these properties both withe original data DERBY_DS that uses the XA driver, and later with a new data source i created on purpose to try to work around the sequencing contengy.
For example:

            
This new DERBY_SEQUENCING_NON_JTA is explicitly configured to use a NON_XA driver with global transactions flag set to disabled.
Regardless, the only thing I get out of this is that the application is deployed and super fast, up to the point where i stress it with a system test that introduces some degreee of concurrency, and then I see the dead locks on the sequencing table.
Meaning that the ongoing transactions are holding tight to their locks on the sequencing table.
Is this a known issue?
Is there something I am missing in the configuration?
It really should not be this diffcult to get eclipse link to run its sequence reads and updates on a separate transaction of the main JTA transaction, but so far looks impossible.
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.3.v20120629-r11760): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
Error Code: 30000
Call: UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?
bind => [2 parameters bound]
Query: DataModifyQuery(name="MyEntity_Gen" sql="UPDATE ID_GEN SET SEQ_VALUE = SEQ_VALUE + ? WHERE SEQ_NAME = ?")
Many thanks for your help.

Are you calling the cmp bean code and your new Sql code under a same transactional context?
The following setting
"rollbackLocalTxUponConnClose=true"
will make the connectionpool to call the rollback method on the connection object before keeping it back in the pool. In your sql code if you are calling connection.close() , then your entire transaction will be rolled back.
CMP bean requires a transactional connection while communicating with the database.
What is the sequence of code execution?
I think you must be calling sql code first and then cmp bean code later.
You may avoid this problem in this way. This is my guess based on my understanding on your code execution.
1. set rollbackLocalTxUponConnClose=false
Execute the sql code and cmp code in a single transaction (in a single session bean method with cmt or bmt transaction ). Specify tx.rollback if it is bmt. or call tx.setRollbackOnly() if it is a cmt. In this way you will have control to roll back the transactions.
Hope this helps you.
bmt-> bean managed transaction
cmt-> container managed transaction.
Regards,
Seshi.

Configure J2EE Server in FB4 beta

Hi,
I think, there are very serious problems with J2EE deployment in FB4 beta2.
1) Can not change or add or delete anything in "Target Runtime".
New button and "Show all runtimes" checkbox don't do anything.   "New" button gets disabled and no way to re-enable it.
Can't unistall Facets either.
Imported my Flex project from FB3. It produced error: "Target Runtime JBoss 5.0 not defined".
So I am going to project Properties/Target Runtime to remove old one and add a "new" JBoss 5.0.
Nothing works (see #1).
2) OK, trying to create a new Flex project, going through Create Flex project wizard.
On page "Configure J2EE Server" it is expecting Server location with existing WEB-INF/flex folder containing flex-config.xml or services-config.xml
But from where, some other existing project ?
Plus, JBoss5 forces you to work with non-exploded archives (WAR, JAR, etc)
How do you resolve that one ?
Am I missing something ?   Or is FB4 beta2 is completely unusable with JBoss 5.1 ?
Is there beta3 or nightly build where it is fixed ?
Please help !
TIA,
Oleg.

Still no solution to that problem ?
Say, I am developing an AIR2 app which has some Java part to it (remoting, Web Service, whatever),
with or without BlazeDS (or LCDS). Anything requiring Web Server (J2EE / servlet container).
How do I add new Server to FB4 beta2 ? Lets say Tomcat 6 or JBoss 5.1.
If I go to Preferences->Server->Runtime Environments, there is only one selection - J2EE Runtime Library (what is that?)
OK, I click Add, then link Download additional server adapters, and in a few seconds prompts for login/pwd for SAP Community Network.
I don't know any... so after I click Cancel, I can only choose Geronimo, GlassFish, Jetty, Weblogic, WASCE.
No Tomcat, No JBoss ?   Nothing like a long selection list in FB3 ?
Search for server runtime environments stops right away.   FB3 can find a dosen ones on my hard disk.
Is it a major hole in FB4 beta2 ?
Makes it pretty useless to me... :-(
Please advise !
Thanks,
Oleg.
Message was edited by: olegkon
Message was edited by: olegkon

Application server 9.0 with mysql

Hello!
I'm using glassfish with application server 9.0 and i want to connect with mysql.
My settings are:
datasource classname: com.mysql.jdbc.jdbc2.optional.MysqlDataSource
resource type: javax.sql.connectionpoolDataSource
ARE OK?
I use mysql connector 3.1.13, 5.0.2 or 3.1.13? which is correct?
Thanks

Hi,
Please take a look at the following blog which talks about using mysql with Glassfish:
http://weblogs.java.net/blog/amyroh/archive/2006/02/roller_21_on_gl_1.html
In this example the driver that she uses is sql-connector-java-3.1.12-bin.jar
Also, she uses the following:
datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource"
which is slightly different to the one that you are using... maybe you should try this....
Also, please take a look at the three furum posts already raised on similar issues to this:
http://forum.sun.com/jive/thread.jspa?threadID=102999
Hope this helps

How do I reuse the existing stand-alone CFM application codes on J2EE CF9

Hi all,
Our ColdFusion installation runs on a stand-alone ColdFusion server. Now we would like to upgrade to ColdFusion 9 with J2EE configuration. Is there a way to 'reuse' the existing ColdFusion application codes on the ColdFusion J2EE, WITHOUT moving these codes into a location under the J2EE?
To clarify my question:
The existing CFM application structure looks like this:
D:\MyCFApp\folder1\....
Under J2EE, the folder structure looks like this:
D:\MyJ2EEHomeDirectory\Adobe_ColdFusion_9.ear\cfusion.war\...
I would like to keep the CF application codes under D:\MyCFApp\folder1\....
I can bring up the CF9 Admin Console just fine. What I would like to see is if there's a way for CF9 to recognize the folders OUTSIDE the J2EE directory structure.
I tried the adding some Mappings on the CF9 Admin Console but no luck.
Any advice/input is greatly appreciated!

The solution is not in CF Admin mappings, but rather in web server mappings. You need to tell your web server how/where to find the CFML files, and then configure the web server (using the CF web server configuration tool) to have it hand CF pages to CF for processing.
You may find helpful information in 2 of the CF docs, the Installation guide, and the Administration and Configuration guide. If you visit any page of the CF9 docs, you'll see all the manuals listed on the left.
That said, the J2EE configuration is the least well-documented of them all, since things can change from app server to app server. You've not even said which app server you're using: jboss, tomcat, glassfish, resin, weblogic, websphere? And each of those have different support for various web servers. So there's a limit to how much Adobe will document about getting such things working.
Also, relatively few in the CF community use the J2EE deployment--and many who do only "play with it", so may only use the built-in dev web servers that many app servers come with. When it comes to configuring things for production and integration with real web servers, they may not have any experience to share.
But if after reading the above you have more specific questions, fire away and perhaps some here can help.
/charlie

About EJB deployment descriptor

Hello. I am developing EJB3 with glassfish and weblogic 10. I know I can use annotations to simplify
deployment without using ejb-jar.xml , sun-ejb-jar.xml, weblogic-ejb-jar.xml. However, I do want to know
how to write these files correctly because they have higher priority when used.
Somebody may give me a template about writing these files? (ejb 3 specification, for ejb2, I can
use xdoclet to generate them).Thanks a lot.

Hi Martin,
you're are right, XDoclet support for OC4J is lacking the most important stuff. In my case I needed explicit mapping of CMR-fields. Of course, manually editing orion-ejb-jar.xml either by using a text editor or JDeveloper is no option at all.
So I've added support for explicit CMR-mapping to the OC4J XDoclet templates. It works but wasn't fun to do as Oracle's documentation of CMR-mapping is highly inconsistent (e.g. text, figures, and example code are not in sync).
As I've done this as part of a services contract, I cannot easily publish the results. I'll ask my client and let you know.
Anyway, orion-ejb-jar.xml will be obsolete by default in OC4J 10.x as Oracle switches to Toplink as the default persistence manager. So again, XDoclet support is needed for generating the Toplink-specific deployment descriptor.
I'd really appreciate Oracle to provide OC4J-specific XDoclet enhancements. This would help OC4J in gaining wider acceptance.
Stefan

Error with @SchemaValidation

Hi,
I’m creating a proxy for webservices with wsimport and JAXWS.
Everything seems to work fine but when I add @SchemaValidation to the webservice class, deployment on Glassfish and Weblogic goes wrong with the error message:
cos-st-restricts.1.1: The type 'DateContentType' is atomic, so its {base type definition}, 'xs:anySimpleType', must be an atomic simple type definition or a built-in primitive datatype
Does anybody know what this means?
Is this a problem with the XSD’s or with SchemaValidation?
Does anyone know a fix or workaround? The XSD’s are given so I can’t change them.
Thank you,
Best regards,
Erik
Complete stacktrace:
[#|2012-06-25T17:08:46.390+0200|SEVERE|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=19;_ThreadName=Thread-2;|Exception while invoking class com.sun.enterprise.web.WebApplication start method
java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: javax.servlet.ServletException: com.sun.xml.ws.transport.http.servlet.WSServletException: WSSERVLET11: failed to parse runtime descriptor: javax.xml.ws.WebServiceException: org.xml.sax.SAXParseException: cos-st-restricts.1.1: The type 'DateContentType' is atomic, so its {base type definition}, 'xs:anySimpleType', must be an atomic simple type definition or a built-in primitive datatype.
     at com.sun.enterprise.web.WebApplication.start(WebApplication.java:138)
     at org.glassfish.internal.data.EngineRef.start(EngineRef.java:130)
     at org.glassfish.internal.data.ModuleInfo.start(ModuleInfo.java:269)
     at org.glassfish.internal.data.ApplicationInfo.start(ApplicationInfo.java:301)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:461)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
     at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
     at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:214)
     at org.glassfish.admin.rest.ResourceUtil.runCommand(ResourceUtil.java:207)
     at org.glassfish.admin.rest.resources.TemplateListOfResource.createResource(TemplateListOfResource.java:148)
     at sun.reflect.GeneratedMethodAccessor762.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
     at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
     at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
     at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
     at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)
     at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
     at com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:134)
     at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
     at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
     at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
     at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
     at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
     at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
     at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
     at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
     at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer._service(GrizzlyContainer.java:182)
     at com.sun.jersey.server.impl.container.grizzly.GrizzlyContainer.service(GrizzlyContainer.java:147)
     at org.glassfish.admin.rest.adapter.RestAdapter.service(RestAdapter.java:148)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
     at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
     at java.lang.Thread.run(Thread.java:662)
Edited by: Erik on 28-jun-2012 4:43

Apparently wsimport used XMLGregorianCalender java attributes which caused the SchemaValidation problem.
I solved it using a jaxb binding file so Calender java objects are used instead.
binding file "bindings.xml":
<?xml version="1.0" encoding="UTF-8" ?>
<jaxb:bindings
version="2.0"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<jaxb:globalBindings>
<jaxb:javaType name="java.util.Calendar" xmlType="xs:dateTime"
parseMethod="javax.xml.bind.DatatypeConverter.parseDateTime"
printMethod="javax.xml.bind.DatatypeConverter.printDateTime"/>
<jaxb:javaType name="java.util.Calendar" xmlType="xs:time"
parseMethod="javax.xml.bind.DatatypeConverter.parseTime"
printMethod="javax.xml.bind.DatatypeConverter.printTime"/>
<jaxb:javaType name="java.util.Calendar" xmlType="xs:date"
parseMethod="javax.xml.bind.DatatypeConverter.parseDate"
printMethod="javax.xml.bind.DatatypeConverter.printDate"/>
<jaxb:serializable uid="1"/>
</jaxb:globalBindings>
</jaxb:bindings>
and added "-b bindings.xml" to the wsimport command:
wsimport -keep -Xnocompile -b bindings.xml some.wsdl
Extra adapter.java files are generated for the conversion, don't forget to use them in your java project.
Hope someone else will find this useful as well!

PXIe Development Kit

Based on Xilinx V5 FPGA.
Compatible with NI PXIe Chassis.
Attachments:
CPCIe_Dev_Kit_V2.pdf ‏326 KB

You might want to ask this on the Java forum - but if you want to run a servlet you need a Java EE server - something like Glassfish or WebLogic or Tomcat.
The Java forums are here:
https://forums.oracle.com/forums/category.jspa?categoryID=285
Right now you are in the JDeveloper forum - and by the way, if you download JDeveloper you'll get everything you need to develop and test run your servlet.

Configure j2ee server

hi
i am fuad
iam tring to use j2ee server but i don't know what is the configuration that should be done
so if some one can help me what that ponit
before iam using tomcat now i want use tamcat
thank you

Still no solution to that problem ?
Say, I am developing an AIR2 app which has some Java part to it (remoting, Web Service, whatever),
with or without BlazeDS (or LCDS). Anything requiring Web Server (J2EE / servlet container).
How do I add new Server to FB4 beta2 ? Lets say Tomcat 6 or JBoss 5.1.
If I go to Preferences->Server->Runtime Environments, there is only one selection - J2EE Runtime Library (what is that?)
OK, I click Add, then link Download additional server adapters, and in a few seconds prompts for login/pwd for SAP Community Network.
I don't know any... so after I click Cancel, I can only choose Geronimo, GlassFish, Jetty, Weblogic, WASCE.
No Tomcat, No JBoss ? Nothing like a long selection list in FB3 ?
Search for server runtime environments stops right away. FB3 can find a dosen ones on my hard disk.
Is it a major hole in FB4 beta2 ?
Makes it pretty useless to me... :-(
Please advise !
Thanks,
Oleg.
Message was edited by: olegkon
Message was edited by: olegkon

Manual JNDI lookup for EJB3 between different Application Server Instances

Hi all,
i have spent quite some time looking into this problem and searching the net but i just can't figure out for the life of me what i am doing wrong so i hope someone here can give me a clue or a good resource where i can look it up myself.
I am currently doing some interoperability tests concerning EJB calls between Glassfish and Weblogic 10. In my test setup i have an EJB deployed in a jar file on one server and a servlet in a war file deployed on the other. The objective is to try to look up and call the EJB from the servlet. As there seem to be some issues with injection in Weblogic 10 i set that one aside for now (i have opened a case at BEA support for this) but i would like to do a plain old JNDI lookup to obtain the EJB.
The online tutorials and FAQs i have read so far all state that this can be done the same way as it works for EJB2.x, at least if i understood them correctly. The interessting thing is, when i deploy an EJB2.x bean i can look it up without problems, but when i try to do the same with the EJB3 bean the name cannot be found. On the other hand when listing all contents of the JNDI tree in Glassfish from a stand alone application i can see entries for both EJBs of the type java.naming.Reference (in Weblogic i can also see entries for both, but the ones for EJB3 are of some weird internal weblogic types, which i put down as a weblogic problem for now).
The lookup code for the servlet running in weblogic looks like this:
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "corbaname:iiop:1.2@localhost:3700");
Object myEjb = new InitialContext(env).lookup("JNDINameDisplayedByContextListing");
I know that the preferred way would be to have the corbaname put into weblogic.xml/sun-web.xml and just use an InitialContext without an environment to perform the lookup but i wanted to get rid of any additional indirections to pinpoint the source my problem and it should work this way, too. As i said, it works when i target an EJB2.x bean but not with the EJB3 one, so i guess i am doing something wrong there. The jar file contains the interface of the bean annotated with @Remote and the implementation of the interface annotated with @Stateless, i also tried setting the mappedName attribute for the bean and use that name as JNDI name, but that also fails. In addition i added an ejb-jar.xml to the jars META-INF containing the following:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
     version="3.0">
     <enterprise-beans>
          <session>
               <ejb-name>SecurityTest3EJB</ejb-name>
               <ejb-class>
                    testcase.ejb.SecurityTestBean
               </ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
But the ejb-name specified there does not show up in a context listing, so i would guess that means the file is ignored or only accessible from within the same application server (note, there is no indication of any problems in the Glassfish log when deploying the jar file).
This might be just a stupid mistake by me, but i just can't figure it out at the moment, so any advice will be greatly appriciated.
Thanks, Chris

I think i stumbled across something now. From some posts it seems to me that the EJB3 spec does not require EJBs to be accessible from a remote location, since this can be achieved by using the @RemoteHome annotation and performing a EJB2.x compliant look up. Is that correct?

Development kit which includes the javax.servlet package

Which java development kit(s) contain the javax.servlet package.v I can't seem to find one. Thanks

You might want to ask this on the Java forum - but if you want to run a servlet you need a Java EE server - something like Glassfish or WebLogic or Tomcat.
The Java forums are here:
https://forums.oracle.com/forums/category.jspa?categoryID=285
Right now you are in the JDeveloper forum - and by the way, if you download JDeveloper you'll get everything you need to develop and test run your servlet.

Setting EJB JNDI name

Hi all !
I have one EJB application which needs to be run in two different containers (GlassFish
and Weblogic)
One issue I have faced is the JNDI binding. When I deploy my EJB, the jndiBinding of @RemoteBinding
is not used:
@Stateless
@RemoteBinding(jndiBinding="UserManagerEJB/remote")
public class UserManagerBean implements UserManagerEJB{
rather the EJB is bound at JAR_NAME_jarUserManagerBean_UserManagerEJB
is it possible to bind the EJB at "UserManagerEJB/remote" so that it's portable between the two App. servers?
thanks
Frank

I could not find RemoteBinding in the following doc :-
Link :[http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb30/annotations.html]
I wonder whether this would work. I am not sure whether this is implemented.

How to send to Weblogic 9.1 JMS queue from EJB running in Glassfish?

Hi.
I hope this is the correct forum.
I need to send a message to a jms queue on a remote weblogic 9.1 server. To this end I believe I will have to:
1) Install one or more weblogic client libraries/jar files on my glassfish application server. The weblogic server expects communication in the "t3" protocol, which I believe tunnels iiop, jms etc. inside their own proprietary protocol
2) Define the jms queue in my glassfish application server with a queue connection factory that creates the queue using classes from the weblogic jars?
3) Otherwise code the EJB methods sending messages as I would code and send messages to any jms queue
It's the first two steps that have me baffled. The more I dig in glassfish administrator's manual, the more confused I become.
Anybody have any idea if/how this can be accomplished?
Some reference to where I may find information as to how to accomplish this?
Thank you,
Jacob.

Jacob,
I suggest you try, either a GlassFish forum (http://forums.java.net/jive/forum.jspa?forumID=56), or perhaps the GenericJMSRA project https://genericjmsra.dev.java.net .This forum is primarily about the Sun JMS provider, Java MQ or Open MQ -- or the JMS Specification.
-- Ed Bratt

Glassfish vs weblogic

Similar Messages

Maybe you are looking for