Re: Stateful Session Bean NoSuchObjectException

2008-07-09 Thread David Blevins


On Jul 9, 2008, at 9:12 PM, fmchale wrote:



Thanks Kevan this works great, do you know if this has to be set for  
the

whole of openejb or can it be set on  a ejb by ejb basis?


It's possible to configure a second stateful container with a  
different timeout and deploy some beans in the no timeout container  
and other beans into the short timeout container.


There isn't much doc on this, so if you'd like to try it let me know  
and we can blaze that trail together.


-David


Kevan Miller wrote:



On Jul 9, 2008, at 9:46 PM, fmchale wrote:



Hello,

After much research I have become completely stumped and confused on
this
issue (pardon me as well if its something simple, I am learning JEE
development).  I currently have a Stateful Session bean that is
accessed by
web clients.  After approximately 20 minutes I get a
NoSuchObjectException -
Stateful Session Bean has timed out.  Is there anyway I can set the
timeout
to be longer then 20 minutes. Im assuming that after 20 minutes the
timeout
occurs and instead of passivating the bean is completely destroyed.
Here is
a snippet of important bean parts.

public @Stateful class InternTempBean implements InternTemp{

@PersistenceContext(unitName="MatchMakerModel",
type=PersistenceContextType.EXTENDED)
EntityManager emMatchMaker;

public InternTempBean(){
}

  .. some more bean methods

@Remove
public void mergeIntern(Intern_Temp intern){
emMatchMaker.merge(intern);
}

I was thinking maybe there was some setting I could tell openejb to
not
timeout after 20 minutes.
Can anyone guide me in the right direction here.


As you've figured out, the default timeout is 20 minutes.

To alter this default:

1. stop your server
2. edit var/config/config.xml
3. locate the openejb module element and make it looks something  
like:




${OpenEJBPort + PortOffset}
${ServerHostname}


PoolSize=1000
  TimeOut=30



For an infinite TimeOut, set the value to 0.

--kevan




--
View this message in context: 
http://www.nabble.com/Stateful-Session-Bean-NoSuchObjectException-tp18374356s134p18375532.html
Sent from the Apache Geronimo - Users mailing list archive at  
Nabble.com.







Re: Stateful Session Bean NoSuchObjectException

2008-07-09 Thread fmchale

Thanks Kevan this works great, do you know if this has to be set for the
whole of openejb or can it be set on  a ejb by ejb basis?

Kevan Miller wrote:
> 
> 
> On Jul 9, 2008, at 9:46 PM, fmchale wrote:
> 
>>
>> Hello,
>>
>> After much research I have become completely stumped and confused on  
>> this
>> issue (pardon me as well if its something simple, I am learning JEE
>> development).  I currently have a Stateful Session bean that is  
>> accessed by
>> web clients.  After approximately 20 minutes I get a  
>> NoSuchObjectException -
>> Stateful Session Bean has timed out.  Is there anyway I can set the  
>> timeout
>> to be longer then 20 minutes. Im assuming that after 20 minutes the  
>> timeout
>> occurs and instead of passivating the bean is completely destroyed.   
>> Here is
>> a snippet of important bean parts.
>>
>> public @Stateful class InternTempBean implements InternTemp{
>>
>>  @PersistenceContext(unitName="MatchMakerModel",
>> type=PersistenceContextType.EXTENDED)
>>  EntityManager emMatchMaker;
>>  
>>  public InternTempBean(){
>>  }
>>
>>.. some more bean methods
>>
>>  @Remove
>>  public void mergeIntern(Intern_Temp intern){
>>  emMatchMaker.merge(intern);
>>  }
>>
>> I was thinking maybe there was some setting I could tell openejb to  
>> not
>> timeout after 20 minutes.
>> Can anyone guide me in the right direction here.
> 
> As you've figured out, the default timeout is 20 minutes.
> 
> To alter this default:
> 
> 1. stop your server
> 2. edit var/config/config.xml
> 3. locate the openejb module element and make it looks something like:
> 
>  
>  
>  ${OpenEJBPort + PortOffset} attribute>
>  ${ServerHostname}
>  
>  
>  PoolSize=1000
>TimeOut=30
>  
>  
> 
> For an infinite TimeOut, set the value to 0.
> 
> --kevan
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Stateful-Session-Bean-NoSuchObjectException-tp18374356s134p18375532.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.



Re: Stateful Session Bean NoSuchObjectException

2008-07-09 Thread Kevan Miller


On Jul 9, 2008, at 9:46 PM, fmchale wrote:



Hello,

After much research I have become completely stumped and confused on  
this

issue (pardon me as well if its something simple, I am learning JEE
development).  I currently have a Stateful Session bean that is  
accessed by
web clients.  After approximately 20 minutes I get a  
NoSuchObjectException -
Stateful Session Bean has timed out.  Is there anyway I can set the  
timeout
to be longer then 20 minutes. Im assuming that after 20 minutes the  
timeout
occurs and instead of passivating the bean is completely destroyed.   
Here is

a snippet of important bean parts.

public @Stateful class InternTempBean implements InternTemp{

@PersistenceContext(unitName="MatchMakerModel",
type=PersistenceContextType.EXTENDED)
EntityManager emMatchMaker;

public InternTempBean(){
}

   .. some more bean methods

@Remove
public void mergeIntern(Intern_Temp intern){
emMatchMaker.merge(intern);
}

I was thinking maybe there was some setting I could tell openejb to  
not

timeout after 20 minutes.
Can anyone guide me in the right direction here.


As you've figured out, the default timeout is 20 minutes.

To alter this default:

1. stop your server
2. edit var/config/config.xml
3. locate the openejb module element and make it looks something like:




${OpenEJBPort + PortOffset}attribute>

${ServerHostname}


PoolSize=1000
  TimeOut=30



For an infinite TimeOut, set the value to 0.

--kevan


Stateful Session Bean NoSuchObjectException

2008-07-09 Thread fmchale

Hello,

After much research I have become completely stumped and confused on this
issue (pardon me as well if its something simple, I am learning JEE
development).  I currently have a Stateful Session bean that is accessed by
web clients.  After approximately 20 minutes I get a NoSuchObjectException -
Stateful Session Bean has timed out.  Is there anyway I can set the timeout
to be longer then 20 minutes. Im assuming that after 20 minutes the timeout
occurs and instead of passivating the bean is completely destroyed.  Here is
a snippet of important bean parts.

public @Stateful class InternTempBean implements InternTemp{

@PersistenceContext(unitName="MatchMakerModel",
type=PersistenceContextType.EXTENDED)
EntityManager emMatchMaker;

public InternTempBean(){
}

.. some more bean methods

@Remove
public void mergeIntern(Intern_Temp intern){
emMatchMaker.merge(intern);
}

I was thinking maybe there was some setting I could tell openejb to not
timeout after 20 minutes.
Can anyone guide me in the right direction here.

Thanks,
Fred

-- 
View this message in context: 
http://www.nabble.com/Stateful-Session-Bean-NoSuchObjectException-tp18374356s134p18374356.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.



Multi-homed geronimo woes

2008-07-09 Thread Peter L. Berghold
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi folks,

I have a server with 4 IP addresses associated with it and I'm trying to
get Geronimo to listen to three of the four IP addresses.

Here is an excerpt from my configuration file: (names have been changed
to protect the innocent)


org.apache.catalina.core.StandardHost
name=www.mumble.net
   appBase=
   workDir=work


org.apache.catalina.core.StandardHost
name=www.grumble.org
   appBase=
   workDir=work


org.apache.catalina.core.StandardHost
name=www.whine.org
   appBase=
   workDir=work



In my /etc/hosts file I have:

127.0.0.1 localhost www.mumble.net
127.0.0.1 localhost www.whine.org
127.0.0.1 localhost www.grumble.org

The websites I have associated with mumble and grumble work just fine
but whine does not.

If I do a telnet to port 80 to the IP addresses associated with mumble
and grumble I get a response.  When I telnet to port 80 for whine's
address I get no response.

Now.. I may be about to answer my own question here, but I just moved
whine's DNS records today.  Might this be a case where DNS has not
caught up with reality and geronimo is just confused?




- --

Peter L. Berghold http://www.berghold.net   [EMAIL PROTECTED]
Unix Professional Dog Agility Fan   Crazed Cook
"Those who fail to learn from history are condemned to repeat it."

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIdQvWUM9/01RIhaARArB4AKCZ6oGMpoUWT9YxIostOI2n7asKEgCfZYiL
1IK6XwBOb+iy0AIM9K/4XbI=
=0Gi+
-END PGP SIGNATURE-


Re: Stateful Session Bean Problem Geronimo 2.1.1: "Passivation Failed"

2008-07-09 Thread David Blevins


On Jul 9, 2008, at 3:43 AM, the666pack wrote:



hello,

my old question about stateless session beans was posted here

http://www.nabble.com/Re%3A-Geronimo-2.0.2---OpenEJB-%22Passivation-Failed%22-td16144020s134.html#a16024338

it was concerned about the "passivation bug" in the geronimo 2.0.2  
version.
so i now installed the 2.1.1 version in order to test the stateful  
session

bean performance of geronimo.

unfortunately i still get the problem: "passivation failed" (see  
stack trace

below)...

Was this passivation issue ever solved? or is it still not working  
properly?
i just can turn passivation off, what leads to an inferior  
performance.


The original issue you had was "java.io.NotSerializableException:  
vt.bean.stateful.WriteDataBean" and was fixed with http://issues.apache.org/jira/browse/OPENEJB-215 
 which is in 2.1.1.


The serialization of the EntityManager may or may not be a bug.  Are  
you using a Container-Managed EntityManager (i.e. looked up or  
injected) or a Bean-Managed EntityManager (created yourself via an  
EntityManagerFactory) ?


-David


stack trace:

[exec] 12:38:15,811 INFO  [OpenEJB] Passivating to file
/usr/local/geronimo/5.2.1.1/var/temp/ 
11d1def534ea1be0=-49fa44bf=11b07642b72=-7fe7

[exec] 12:38:15,816 ERROR [OpenEJB] Passivation failed
[exec] java.io.NotSerializableException:
org.apache.openjpa.persistence.EntityManagerImpl
[exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
[exec] at
java 
.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java: 
1509)

[exec] at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java: 
1474)

[exec] at
java 
.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java: 
1392)

[exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
[exec] at
java 
.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java: 
1509)

[exec] at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java: 
1474)

[exec] at
java 
.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java: 
1392)

[exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
[exec] at
java 
.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java: 
1509)

[exec] at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java: 
1474)

[exec] at
java 
.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java: 
1392)

[exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
[exec] at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
[exec] at
org 
.apache 
.openejb 
.core.stateful.SimplePassivater.passivate(SimplePassivater.java:73)

[exec] at
org 
.apache 
.openejb 
.core.stateful.SimplePassivater.passivate(SimplePassivater.java:92)

[exec] at
org 
.apache 
.openejb 
.core 
.stateful 
.StatefulInstanceManager.passivate(StatefulInstanceManager.java:496)

[exec] at
org.apache.openejb.core.stateful.StatefulInstanceManager 
$BeanEntryQueue.add(StatefulInstanceManager.java:610)

[exec] at
org 
.apache 
.openejb 
.core 
.stateful 
.StatefulInstanceManager.poolInstance(StatefulInstanceManager.java: 
429)

[exec] at
org 
.apache 
.openejb 
.core 
.stateful.StatefulContainer.createEJBObject(StatefulContainer.java: 
314)

[exec] at
org 
.apache 
.openejb 
.core.stateful.StatefulContainer.invoke(StatefulContainer.java:267)

[exec] at
org 
.apache 
.openejb 
.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267)

[exec] at
org 
.apache 
.openejb 
.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158)

[exec] at
org 
.apache 
.openejb 
.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:245)

[exec] at
org 
.apache 
.openejb 
.util 
.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)

[exec] at $Proxy22.create(Unknown Source)
[exec] at
org 
.apache 
.openejb 
.core 
.ivm 
.naming 
.BusinessRemoteReference.getObject(BusinessRemoteReference.java:33)

[exec] at
org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java: 
150)

[exec] at
org 
.apache 
.openejb 
.core 
.ivm.naming.IntraVmJndiReference.getObject(IntraVmJndiReference.java: 
38)

[exec] at
org 
.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java: 
40)

[exec] at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java: 
61)

[exec] at
org 
.apache 
.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:118)

[exec] at
org 
.apache 
.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617)

[exec] at
org 
.apache 
.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158)

[exec] at
org 
.apache 
.xbean.naming.context.AbstractCon

Re: Geronimo-2.1.2-SNAPSHOT, Servlet.service() for servlet login-page threw exception

2008-07-09 Thread jklcom99

It's packaged in another jar (IBMLAP.jar and that is in ear/lib)


djencks wrote:
> 
> I don't think you've given enough info to help.  Where is the EULA?   
> Where does the ibm software expect it to be?
> 
> thanks
> david jencks
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Geronimo-2.1.2-SNAPSHOT%2C-Servlet.service%28%29-for-servlet-login-page-threw-exception-tp18363273s134p18367998.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.



Re: Geronimo-2.1.2-SNAPSHOT, Servlet.service() for servlet login-page threw exception

2008-07-09 Thread David Jencks
I don't think you've given enough info to help.  Where is the EULA?   
Where does the ibm software expect it to be?


thanks
david jencks

On Jul 9, 2008, at 8:08 AM, jklcom99 wrote:



I thought by moving all dependency jars to ear/lib directory and  
they would

be seen by all modules.

Now that I have cleared out the manifest classpath in all my jars.
MyApp.jar is referencing other jars which are now placed within ear/ 
lib.

But I'm getting this error.  Am I missing something?

[java] Geronimo Application Server started
[java] Exited with: 19
[java] 16:58:57,596 ERROR [[login-page]] Servlet.service() for  
servlet

login-page threw exception
[java] java.lang.NullPointerException
[java] at java.io.Reader.(Reader.java:61)
[java] at
java.io.InputStreamReader.(InputStreamReader.java:80)
[java] at
com.ibm.lex.lapapp.License.retrieveLicenseAgreement(Unknown S
ource)
[java] at  
com.ibm.lex.lapapp.License.getLicenseAgreement(Unknown

Source
)
[java] at com.ibm.lex.lapapp.License.getLicense(Unknown  
Source)

[java] at
com.ibm.lex.lapapp.LicenseAcceptanceProcess.getLicenseAgreeme
nt(Unknown Source)
[java] at  
com.ibm.lex.lapapp.APP_JLAP.getHtmlLicenseAgreement(Unkno

wn Source)
[java] at app.web.servlet.AppServlet.sendEulaToClient(EulaSer
vlet.java:55)
[java] at app.web.servlet.AppServlet.doGet(AppServlet.java:3
6)
[java] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
[java] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
[java] at
org.apache.catalina.core.ApplicationFilterChain.internalDoFil
ter(ApplicationFilterChain.java:290)
[java] at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl
icationFilterChain.java:206)
[java] at
org.apache.catalina.core.StandardWrapperValve.invoke(Standard
WrapperValve.java:233)
[java] at
org.apache.catalina.core.StandardContextValve.invoke(Standard
ContextValve.java:175)
[java] at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(D
efaultSubjectValve.java:56)
[java] at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMeth
odValve.invoke(GeronimoStandardContext.java:406)
[java] at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.inv
oke(GeronimoBeforeAfterValve.java:47)
[java] at
org.apache.catalina.core.StandardHostValve.invoke(StandardHos
tValve.java:128)
[java] at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor
tValve.java:102)
[java] at
org.apache.catalina.core.StandardEngineValve.invoke(StandardE
ngineValve.java:109)
[java] at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogVal
ve.java:568)
[java] at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAda
pter.java:286)
[java] at
org.apache.coyote.http11.Http11Processor.process(Http11Proces
sor.java:844)
[java] at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandl
er.process(Http11Protocol.java:583)
[java] at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint
.java:447)
[java] at java.lang.Thread.run(Thread.java:619)
--
View this message in context: 
http://www.nabble.com/Geronimo-2.1.2-SNAPSHOT%2C-Servlet.service%28%29-for-servlet-login-page-threw-exception-tp18363273s134p18363273.html
Sent from the Apache Geronimo - Users mailing list archive at  
Nabble.com.






Re: JCA Connector and hidden-classes

2008-07-09 Thread David Jencks

I'm not sure exactly what you are trying to do but have you looked at

http://cwiki.apache.org/GMOxDOC21/configuring-application-specific-logging-with-log4j.html

to see if it would help?

thanks
david jencks

On Jul 9, 2008, at 2:44 AM, johnxmas wrote:


Kevan,

I corrected my geronimo.bat, by suppressing the quotes as you  
stated, and,
yes, it succeeded: the commons-logging.jar used is the one from my  
application


Thanks for that

BUT, that is not a full success: as expected, the LogFactory gives  
me a Log4JLogger


MockAdapter setting hostName - Log is  
org.apache.commons.logging.impl.Log4JLogger - loaded from file:/D:/ 
geronimo-tomcat6-jee5-2.0.2/repository/mock/jca/MockAdapter/1.0/ 
MockAdapter-1.0.rar/rar/commons-logging-1.1.jar


Alas,  the following line

MockAdapter - embedded Log is org.apache.log4j.Logger - loaded from  
file:/D:/geronimo-tomcat6-jee5-2.0.2/lib/log4j-1.2.14.jar


shows that my applications log4j.jar is not used. So, my local  
log4j.xml is ignored and I get a default "INFO" trace level instead

of the ones I specified

Jean-Noël





On Jul 8, 2008, at 9:24 AM, johnxmas wrote:


David,



Hmm. The MPCLSearchOption is working for me. I set as follows:

set JAVA_OPTS=- 
DXorg.apache.geronimo.kernel.config.MPCLSearchOption=safe


I verified that this works on Windows (and Mac OS X). I had Jetty
installed. Don't see how a Tomcat install could behave differently.

Here's the output during deploy:

MockAdapter setting hostName - Log factory is
org.apache.commons.logging.LogFactory - loaded from file:/C:/ 
geronimo-

jetty6-jee5-2.0.2/repository/mock/jca/MockAdapter/1.0/
MockAdapter-1.0.rar/rar/commons-logging.jar

Doh... I bet the " " 's that you used are wrong... If you update your
GERONIMO_OPTS setting in geronimo.bat and remove the quotation mark
characters, I bet it works...

Still need to fix this properly...

--kevan







Geronimo-2.1.2-SNAPSHOT, Servlet.service() for servlet login-page threw exception

2008-07-09 Thread jklcom99

I thought by moving all dependency jars to ear/lib directory and they would
be seen by all modules.

Now that I have cleared out the manifest classpath in all my jars. 
MyApp.jar is referencing other jars which are now placed within ear/lib. 
But I'm getting this error.  Am I missing something?

 [java] Geronimo Application Server started
 [java] Exited with: 19
 [java] 16:58:57,596 ERROR [[login-page]] Servlet.service() for servlet
login-page threw exception
 [java] java.lang.NullPointerException
 [java] at java.io.Reader.(Reader.java:61)
 [java] at
java.io.InputStreamReader.(InputStreamReader.java:80)
 [java] at
com.ibm.lex.lapapp.License.retrieveLicenseAgreement(Unknown S
ource)
 [java] at com.ibm.lex.lapapp.License.getLicenseAgreement(Unknown
Source
)
 [java] at com.ibm.lex.lapapp.License.getLicense(Unknown Source)
 [java] at
com.ibm.lex.lapapp.LicenseAcceptanceProcess.getLicenseAgreeme
nt(Unknown Source)
 [java] at com.ibm.lex.lapapp.APP_JLAP.getHtmlLicenseAgreement(Unkno
wn Source)
 [java] at app.web.servlet.AppServlet.sendEulaToClient(EulaSer
vlet.java:55)
 [java] at app.web.servlet.AppServlet.doGet(AppServlet.java:3
6)
 [java] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
 [java] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
 [java] at
org.apache.catalina.core.ApplicationFilterChain.internalDoFil
ter(ApplicationFilterChain.java:290)
 [java] at
org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl
icationFilterChain.java:206)
 [java] at
org.apache.catalina.core.StandardWrapperValve.invoke(Standard
WrapperValve.java:233)
 [java] at
org.apache.catalina.core.StandardContextValve.invoke(Standard
ContextValve.java:175)
 [java] at
org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(D
efaultSubjectValve.java:56)
 [java] at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMeth
odValve.invoke(GeronimoStandardContext.java:406)
 [java] at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.inv
oke(GeronimoBeforeAfterValve.java:47)
 [java] at
org.apache.catalina.core.StandardHostValve.invoke(StandardHos
tValve.java:128)
 [java] at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor
tValve.java:102)
 [java] at
org.apache.catalina.core.StandardEngineValve.invoke(StandardE
ngineValve.java:109)
 [java] at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogVal
ve.java:568)
 [java] at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAda
pter.java:286)
 [java] at
org.apache.coyote.http11.Http11Processor.process(Http11Proces
sor.java:844)
 [java] at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandl
er.process(Http11Protocol.java:583)
 [java] at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint
.java:447)
 [java] at java.lang.Thread.run(Thread.java:619)
-- 
View this message in context: 
http://www.nabble.com/Geronimo-2.1.2-SNAPSHOT%2C-Servlet.service%28%29-for-servlet-login-page-threw-exception-tp18363273s134p18363273.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.



Stateful Session Bean Problem Geronimo 2.1.1: "Passivation Failed"

2008-07-09 Thread the666pack

hello,

my old question about stateless session beans was posted here

http://www.nabble.com/Re%3A-Geronimo-2.0.2---OpenEJB-%22Passivation-Failed%22-td16144020s134.html#a16024338

it was concerned about the "passivation bug" in the geronimo 2.0.2 version.
so i now installed the 2.1.1 version in order to test the stateful session
bean performance of geronimo. 

unfortunately i still get the problem: "passivation failed" (see stack trace
below)...

Was this passivation issue ever solved? or is it still not working properly?
i just can turn passivation off, what leads to an inferior performance. 

stack trace:

 [exec] 12:38:15,811 INFO  [OpenEJB] Passivating to file
/usr/local/geronimo/5.2.1.1/var/temp/11d1def534ea1be0=-49fa44bf=11b07642b72=-7fe7
 [exec] 12:38:15,816 ERROR [OpenEJB] Passivation failed
 [exec] java.io.NotSerializableException:
org.apache.openjpa.persistence.EntityManagerImpl
 [exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
 [exec] at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
 [exec] at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
 [exec] at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
 [exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
 [exec] at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
 [exec] at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
 [exec] at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
 [exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
 [exec] at
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
 [exec] at
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
 [exec] at
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
 [exec] at
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
 [exec] at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
 [exec] at
org.apache.openejb.core.stateful.SimplePassivater.passivate(SimplePassivater.java:73)
 [exec] at
org.apache.openejb.core.stateful.SimplePassivater.passivate(SimplePassivater.java:92)
 [exec] at
org.apache.openejb.core.stateful.StatefulInstanceManager.passivate(StatefulInstanceManager.java:496)
 [exec] at
org.apache.openejb.core.stateful.StatefulInstanceManager$BeanEntryQueue.add(StatefulInstanceManager.java:610)
 [exec] at
org.apache.openejb.core.stateful.StatefulInstanceManager.poolInstance(StatefulInstanceManager.java:429)
 [exec] at
org.apache.openejb.core.stateful.StatefulContainer.createEJBObject(StatefulContainer.java:314)
 [exec] at
org.apache.openejb.core.stateful.StatefulContainer.invoke(StatefulContainer.java:267)
 [exec] at
org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:267)
 [exec] at
org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:158)
 [exec] at
org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:245)
 [exec] at
org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
 [exec] at $Proxy22.create(Unknown Source)
 [exec] at
org.apache.openejb.core.ivm.naming.BusinessRemoteReference.getObject(BusinessRemoteReference.java:33)
 [exec] at
org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:150)
 [exec] at
org.apache.openejb.core.ivm.naming.IntraVmJndiReference.getObject(IntraVmJndiReference.java:38)
 [exec] at
org.apache.openejb.core.ivm.naming.Reference.getContent(Reference.java:40)
 [exec] at
org.apache.xbean.naming.context.ContextUtil.resolve(ContextUtil.java:61)
 [exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:118)
 [exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617)
 [exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158)
 [exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:617)
 [exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:158)
 [exec] at
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:603)
 [exec] at
javax.naming.InitialContext.lookup(InitialContext.java:392)
 [exec] at vt.servlet.AddServlet.doGet(AddServlet.java:46)
 [exec] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
 [exec] at
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
 [exec] at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application

Re: Use of a GBean from a Message EJB

2008-07-09 Thread Janko Heilgeist

Jacek Laskowski wrote:

On Tue, Jul 1, 2008 at 1:40 PM, dsthode
<[EMAIL PROTECTED]> wrote:


I've followed your advice and changed the default namespace to openejb
version 2.2 and added a  element for the  resolution,
but Geronimo keeps failing on deployment with the message that  is
not in geronimo-namespace-1.2 schema but in
http://openejb.apache.org/xml/ns/openejb-jar-2.2, even though you can open
geronimo-naming-1.2 and find  defined in this schema.


Did you happen to sort it out? What was the solution?

Jacek



Hi,

I think I've traced the problem to a bug in OpenEJB:

OpenEJB forces the namespace of the tags  and  to 
"http://geronimo.apache.org/xml/ns/naming-1.2"; in 
container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb2/NamespaceFilter.java 
regardless of the namespace specified in the openejb-jar.xml deployment 
descriptor. On the other hand the "namespace" attributes in the 
@XmlElement annotations in 
container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb2/GbeanRefType.java
are missing for these variables and therefore during the parsing of the 
deployment descriptor the wrong default namespace of 
"http://openejb.apache.org/xml/ns/openejb-jar-2.2"; is expected. The 
patch attached to this mail fixes this by adding the missing attributes.


I used my patched version of OpenEJB with Geronimo to access a GBean 
from a stateless EJB:


openejb-jar.xml:
http://www.openejb.org/xml/ns/openejb-jar-2.2";>


DummyEJB

LocalGBeanName

GlobalGBeanName






geronimo-application.xml:
[...]

[...]

Inside a @PostConstruct of the EJB class:
[...]
InitialContext ic = new InitialContext();
this.theGBean = (TheGBeanClass)
ic.lookup("java:comp/geronimo/env/LocalGBeanName");
[...]

Everything deploys without any errors and the EJB can correctly access 
the GBean and call methods of the GBean. There doesn't seem to be a way 
to actually inject the GBean with something like a @Resource annotation. 
Is this supposed to work or can GBeans only be injected into an EJBs 
JNDI environment and have to be looked up manually?


Anyway, this should fix most of Damians original problems.

Janko
Index: container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb2/GbeanRefType.java
===
--- container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb2/GbeanRefType.java	(revision 674851)
+++ container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb2/GbeanRefType.java	(working copy)
@@ -58,10 +58,11 @@
 extends AbstractNamingEntryType
 {
 
-@XmlElement(name = "ref-name", required = true)
+@XmlElement(name = "ref-name", namespace="http://geronimo.apache.org/xml/ns/naming-1.2";, required = true)
 protected String refName;
-@XmlElement(name = "ref-type")
+@XmlElement(name = "ref-type", namespace="http://geronimo.apache.org/xml/ns/naming-1.2";)
 protected List refType;
+@XmlElement(name = "pattern", namespace = "http://geronimo.apache.org/xml/ns/naming-1.2";)
 protected List pattern;
 
 /**


Multiple 'Service' in GMO 2.1 (like in Tomcat)

2008-07-09 Thread cvx22

Hi gurus,
  I plan to migrate my web-apps from Tomcat6 to Geronimo2.1. I have one
configuration problem. In my tomcat's server.xml I have declared two
Service, like that:

--- part of server.xml -
 

...
   




...
   

--- end part of server.xml -

With that configuration I have two servlet containers under one Tomcat, so I
have different applications for each of them.

How can I make the same in Geronimo???

thanks for help,
-- 
View this message in context: 
http://www.nabble.com/Multiple-%27Service%27-in-GMO-2.1-%28like-in-Tomcat%29-tp18358099s134p18358099.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.



Re: Re: JCA Connector and hidden-classes

2008-07-09 Thread johnxmas
Kevan,

I corrected my geronimo.bat, by suppressing the quotes as you stated, and,
yes, it succeeded: the commons-logging.jar used is the one from my application

Thanks for that

BUT, that is not a full success: as expected, the LogFactory gives me a 
Log4JLogger

MockAdapter setting hostName - Log is 
org.apache.commons.logging.impl.Log4JLogger - loaded from 
file:/D:/geronimo-tomcat6-jee5-2.0.2/repository/mock/jca/MockAdapter/1.0/MockAdapter-1.0.rar/rar/commons-logging-1.1.jar

Alas,  the following line

MockAdapter - embedded Log is org.apache.log4j.Logger - loaded from 
file:/D:/geronimo-tomcat6-jee5-2.0.2/lib/log4j-1.2.14.jar

shows that my applications log4j.jar is not used. So, my local log4j.xml is 
ignored and I get a default "INFO" trace level instead
of the ones I specified

Jean-Noël



>
>On Jul 8, 2008, at 9:24 AM, johnxmas wrote:
>
>> David,

>Hmm. The MPCLSearchOption is working for me. I set as follows:
>
>set JAVA_OPTS=-DXorg.apache.geronimo.kernel.config.MPCLSearchOption=safe
>
>I verified that this works on Windows (and Mac OS X). I had Jetty  
>installed. Don't see how a Tomcat install could behave differently.
>
>Here's the output during deploy:
>
>MockAdapter setting hostName - Log factory is  
>org.apache.commons.logging.LogFactory - loaded from file:/C:/geronimo- 
>jetty6-jee5-2.0.2/repository/mock/jca/MockAdapter/1.0/ 
>MockAdapter-1.0.rar/rar/commons-logging.jar
>
>Doh... I bet the " " 's that you used are wrong... If you update your  
>GERONIMO_OPTS setting in geronimo.bat and remove the quotation mark  
>characters, I bet it works...
>
>Still need to fix this properly...
>
>--kevan
>
>
>