You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Christopher Lenz <cm...@gmx.de> on 2003/04/22 23:34:23 UTC
Problems with containers
Hi Vincent and everyone else who is listening :-)
while implementing and testing the <cactus> task I've been working on,
I've encountered some problems with containers that I've not worked very
much with yet. (On the positive side, the task is now very nicely
working with Tomcat3x, Tomcat4x and Resin2x).
First problem is with Orion. I've tried both 1.6.0b and 2.0.1, but both
have the same problem with the filter redirector. First, as is indicated
in the test web.xml, the filter must be mapped to a "physical" resource.
If that isn't the case, or the resource doesn't exist in the web-app,
Orion returns a "400 Bad Request". If it *is* mapped to an actual,
existing resource, I get "java.net.SocketException: Connection aborted
by peer: socket write error". Weird. Anyone running the filter tests
successfully against Orion?
Second is WebLogic, and is of course more complicated. I'm a complete
newbie to WL, so I feel a bit lost. Should I expect to be able to run
tests against WL-Server 7.0 SP2 out of the box? Obviously, I am not, but
that could easily be an error on my side ;-)
More concretely, the problem I'm seeing is this:
-----------------------------------------------------------------------------
test:
[cactus] Building jar:
c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\applications\test.war
[cactus] Starting WebLogic Server...
[cactus] <22.04.2003 23:04:38 CEST> <Notice> <Management> <140005>
<Loading configuration
c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\.\config.xml>
[cactus] <22.04.2003 23:04:39 CEST> <Critical> <WebLogicServer>
<000364> <Server failed during initialization.
Exception:weblogic.management.configuration.ConfigurationException:
Error parsing the configuration file: Version mismatch. have 30,
expected 1 - with nested exception:
[cactus] [weblogic.security.internal.SerializedSystemIniException:
Version mismatch. have 30, expected 1]
[cactus] weblogic.security.internal.SerializedSystemIniException:
Version mismatch. have 30, expected 1
[cactus] at
weblogic.security.internal.SerializedSystemIni.<init>(SerializedSystemIni.java:117)
[cactus] at
weblogic.security.internal.SerializedSystemIni.getEncryptionService(SerializedSystemIni.java:212)
[cactus] at
weblogic.management.internal.EncryptedData.getEncryptionService(EncryptedData.java:82)
[cactus] at
weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:44)
-----------------------------------------------------------------------------
It seems that the SerializedSystemIni.dat we provide includes version
information, and WL detects an incompatibility. It seems weird to me
that we're providing a binary, serialized file, as those are generally
very fragile.
WL 6.x doesn't seem to be available for download/evaluation anymore, so
I have absolutely no idea how to test that part of the container
support. Any ideas?
Any input much appreciated, as always :-)
--
Christopher Lenz
/=/ cmlenz at gmx.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: Problems with containers
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 23 April 2003 00:42
> To: Cactus Developers List
> Subject: Re: Problems with containers
>
> Hi Vincent,
>
> thanks for the response. As for Orion, I'd be interested to hear
whether
> you have better luck, and what additional steps are necessary (if
any).
> About WebLogic, I'll try to dig into it a bit more, but I'm not sure
> whether time permits. +1 for dropping WL6 support, and instead
focussing
> on current versions (WL8.1).
>
> Another question: I've seen the EnhydraRun class in the Ant
integration,
> but I don't think we have any support for Enhydra apart from that (I
> should add that I've never used Enhydra and have no idea what the
state
> of the thing is). Can you give me a hint about why the EnhydraRun
class
> is there, and where the missing pieces of the puzzle are hiding? :-)
Not long ago we were supporting Enhydra and we had scripts for it (for
Enhydra 3.x). Then Enhydra stopped and was out of business and I dropped
the scripts when performing a build refactoring about 2 months ago. I
had seen that Enhydra was rising again with a new open source project on
SF and Enhydra 5 has been released. They even said in the release note
that they were supporting Cactus! Then some time after I looked again
and did not see any further activity. That said, I have just checked and
there is some activity! I was looking at http://enhydra.enhydra.org/ but
this page seems dead. However, looking at
http://debian-sf.objectweb.org/projects/enhydra brings hope as they seem
to have released the some 5.0 final version on 29th of March 2003 and a
5.1beta7 on 17th of April 2003. Not sure why they don't advertise it.
Anyway, I say we drop EnhydraRun for now and we'll resurrect it when/if
we add back support for Enhydra.
Thanks
-Vincent
>
> Thanks!
>
> Vincent Massol wrote:
> >
> >>-----Original Message-----
> >>From: Christopher Lenz [mailto:cmlenz@gmx.de]
> >>Sent: 22 April 2003 23:34
> >>To: Cactus Developers List
> >>Subject: Problems with containers
> >>
> >>Hi Vincent and everyone else who is listening :-)
> >>
> >>while implementing and testing the <cactus> task I've been working
on,
> >>I've encountered some problems with containers that I've not worked
> >
> > very
> >
> >>much with yet. (On the positive side, the task is now very nicely
> >>working with Tomcat3x, Tomcat4x and Resin2x).
> >
> >
> > cool :-)
> >
> >
> >>First problem is with Orion. I've tried both 1.6.0b and 2.0.1, but
> >
> > both
> >
> >>have the same problem with the filter redirector. First, as is
> >
> > indicated
> >
> >>in the test web.xml, the filter must be mapped to a "physical"
> >
> > resource.
> >
> >>If that isn't the case, or the resource doesn't exist in the
web-app,
> >>Orion returns a "400 Bad Request". If it *is* mapped to an actual,
> >>existing resource, I get "java.net.SocketException: Connection
aborted
> >>by peer: socket write error". Weird. Anyone running the filter tests
> >>successfully against Orion?
> >
> >
> > I had tried it with Orion 1.5.2 and 1.6.0 and it was working. I'll
need
> > to try it again.
> >
> >
> >>Second is WebLogic, and is of course more complicated. I'm a
complete
> >>newbie to WL, so I feel a bit lost. Should I expect to be able to
run
> >>tests against WL-Server 7.0 SP2 out of the box? Obviously, I am not,
> >
> > but
> >
> >>that could easily be an error on my side ;-)
> >
> >
> > It was working for me with WL 6.1 SP3 and 7.0 SP1 if I recall
correctly.
> > I haven't tried it with 7.0 SP2 though.
> >
> >
> >>More concretely, the problem I'm seeing is this:
> >>
> >
> >
------------------------------------------------------------------------
> > --
> >
> >>---
> >>test:
> >> [cactus] Building jar:
> >>
> >
> >
c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\application
> > s\
> >
> >>test.war
> >> [cactus] Starting WebLogic Server...
> >> [cactus] <22.04.2003 23:04:38 CEST> <Notice> <Management>
<140005>
> >><Loading configuration
> >>
> >
> >
c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\.\config.xm
> > l>
> >
> >> [cactus] <22.04.2003 23:04:39 CEST> <Critical> <WebLogicServer>
> >><000364> <Server failed during initialization.
> >>Exception:weblogic.management.configuration.ConfigurationException:
> >>Error parsing the configuration file: Version mismatch. have 30,
> >>expected 1 - with nested exception:
> >> [cactus]
[weblogic.security.internal.SerializedSystemIniException:
> >>Version mismatch. have 30, expected 1]
> >> [cactus]
weblogic.security.internal.SerializedSystemIniException:
> >>Version mismatch. have 30, expected 1
> >> [cactus] at
> >>
> >
> >
weblogic.security.internal.SerializedSystemIni.<init>(SerializedSystemIn
> > i.
> >
> >>java:117)
> >> [cactus] at
> >>
> >
> >
weblogic.security.internal.SerializedSystemIni.getEncryptionService(Seri
> > al
> >
> >>izedSystemIni.java:212)
> >> [cactus] at
> >>
> >
> >
weblogic.management.internal.EncryptedData.getEncryptionService(Encrypte
> > dD
> >
> >>ata.java:82)
> >> [cactus] at
> >>
> >
> >
weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:44
> > )
> >
> >
------------------------------------------------------------------------
> > --
> >
> >>---
> >>
> >>It seems that the SerializedSystemIni.dat we provide includes
version
> >>information, and WL detects an incompatibility. It seems weird to me
> >>that we're providing a binary, serialized file, as those are
generally
> >>very fragile.
> >
> >
> > Sure. However, I could not find a working solution without this
binary
> > file. One solution would be to either copy these files somewhere
from
> > cactus.home.weblogic7x if available or generate them using some
weblogic
> > command line tool. But I'm not sure how to do that unfortunately.
> >
> >
> >>WL 6.x doesn't seem to be available for download/evaluation anymore,
> >
> > so
> >
> >>I have absolutely no idea how to test that part of the container
> >>support. Any ideas?
> >
> >
> > You're right. They seem to be available only for past customers with
> > support contracts
> > (http://commerce.bea.com/siteinfo/previous_releases.jsp). So I say
we
> > drop support for WL 6.x. Better to add support for the 8.x series...
:-)
> >
> >
> >>Any input much appreciated, as always :-)
> >
> >
> > I'm not of much help. I haven't been playing with the latest
containers
> > lately. This is one of the reasons I'd like to externalize container
> > configuration and start/stop/deploy from Cactus in the medium term
and
> > put it in a project on its own. Maybe the new <cactus> Ant task
> > implementation could be used as the base for this new project once
it is
> > finished (but of course keeping the Ant part in Cactus).
> >
> > Thanks Chris!
> > -Vincent
> >
> >
> >>--
> >>Christopher Lenz
> >>/=/ cmlenz at gmx.de
> >>
> >>
>
>>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
> >
> >
>
>
> --
> Christopher Lenz
> /=/ cmlenz at gmx.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Problems with containers
Posted by Christopher Lenz <cm...@gmx.de>.
Hi Vincent,
thanks for the response. As for Orion, I'd be interested to hear whether
you have better luck, and what additional steps are necessary (if any).
About WebLogic, I'll try to dig into it a bit more, but I'm not sure
whether time permits. +1 for dropping WL6 support, and instead focussing
on current versions (WL8.1).
Another question: I've seen the EnhydraRun class in the Ant integration,
but I don't think we have any support for Enhydra apart from that (I
should add that I've never used Enhydra and have no idea what the state
of the thing is). Can you give me a hint about why the EnhydraRun class
is there, and where the missing pieces of the puzzle are hiding? :-)
Thanks!
Vincent Massol wrote:
>
>>-----Original Message-----
>>From: Christopher Lenz [mailto:cmlenz@gmx.de]
>>Sent: 22 April 2003 23:34
>>To: Cactus Developers List
>>Subject: Problems with containers
>>
>>Hi Vincent and everyone else who is listening :-)
>>
>>while implementing and testing the <cactus> task I've been working on,
>>I've encountered some problems with containers that I've not worked
>
> very
>
>>much with yet. (On the positive side, the task is now very nicely
>>working with Tomcat3x, Tomcat4x and Resin2x).
>
>
> cool :-)
>
>
>>First problem is with Orion. I've tried both 1.6.0b and 2.0.1, but
>
> both
>
>>have the same problem with the filter redirector. First, as is
>
> indicated
>
>>in the test web.xml, the filter must be mapped to a "physical"
>
> resource.
>
>>If that isn't the case, or the resource doesn't exist in the web-app,
>>Orion returns a "400 Bad Request". If it *is* mapped to an actual,
>>existing resource, I get "java.net.SocketException: Connection aborted
>>by peer: socket write error". Weird. Anyone running the filter tests
>>successfully against Orion?
>
>
> I had tried it with Orion 1.5.2 and 1.6.0 and it was working. I'll need
> to try it again.
>
>
>>Second is WebLogic, and is of course more complicated. I'm a complete
>>newbie to WL, so I feel a bit lost. Should I expect to be able to run
>>tests against WL-Server 7.0 SP2 out of the box? Obviously, I am not,
>
> but
>
>>that could easily be an error on my side ;-)
>
>
> It was working for me with WL 6.1 SP3 and 7.0 SP1 if I recall correctly.
> I haven't tried it with 7.0 SP2 though.
>
>
>>More concretely, the problem I'm seeing is this:
>>
>
> ------------------------------------------------------------------------
> --
>
>>---
>>test:
>> [cactus] Building jar:
>>
>
> c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\application
> s\
>
>>test.war
>> [cactus] Starting WebLogic Server...
>> [cactus] <22.04.2003 23:04:38 CEST> <Notice> <Management> <140005>
>><Loading configuration
>>
>
> c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\.\config.xm
> l>
>
>> [cactus] <22.04.2003 23:04:39 CEST> <Critical> <WebLogicServer>
>><000364> <Server failed during initialization.
>>Exception:weblogic.management.configuration.ConfigurationException:
>>Error parsing the configuration file: Version mismatch. have 30,
>>expected 1 - with nested exception:
>> [cactus] [weblogic.security.internal.SerializedSystemIniException:
>>Version mismatch. have 30, expected 1]
>> [cactus] weblogic.security.internal.SerializedSystemIniException:
>>Version mismatch. have 30, expected 1
>> [cactus] at
>>
>
> weblogic.security.internal.SerializedSystemIni.<init>(SerializedSystemIn
> i.
>
>>java:117)
>> [cactus] at
>>
>
> weblogic.security.internal.SerializedSystemIni.getEncryptionService(Seri
> al
>
>>izedSystemIni.java:212)
>> [cactus] at
>>
>
> weblogic.management.internal.EncryptedData.getEncryptionService(Encrypte
> dD
>
>>ata.java:82)
>> [cactus] at
>>
>
> weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:44
> )
>
> ------------------------------------------------------------------------
> --
>
>>---
>>
>>It seems that the SerializedSystemIni.dat we provide includes version
>>information, and WL detects an incompatibility. It seems weird to me
>>that we're providing a binary, serialized file, as those are generally
>>very fragile.
>
>
> Sure. However, I could not find a working solution without this binary
> file. One solution would be to either copy these files somewhere from
> cactus.home.weblogic7x if available or generate them using some weblogic
> command line tool. But I'm not sure how to do that unfortunately.
>
>
>>WL 6.x doesn't seem to be available for download/evaluation anymore,
>
> so
>
>>I have absolutely no idea how to test that part of the container
>>support. Any ideas?
>
>
> You're right. They seem to be available only for past customers with
> support contracts
> (http://commerce.bea.com/siteinfo/previous_releases.jsp). So I say we
> drop support for WL 6.x. Better to add support for the 8.x series... :-)
>
>
>>Any input much appreciated, as always :-)
>
>
> I'm not of much help. I haven't been playing with the latest containers
> lately. This is one of the reasons I'd like to externalize container
> configuration and start/stop/deploy from Cactus in the medium term and
> put it in a project on its own. Maybe the new <cactus> Ant task
> implementation could be used as the base for this new project once it is
> finished (but of course keeping the Ant part in Cactus).
>
> Thanks Chris!
> -Vincent
>
>
>>--
>>Christopher Lenz
>>/=/ cmlenz at gmx.de
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
>
>
--
Christopher Lenz
/=/ cmlenz at gmx.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: Problems with containers
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 22 April 2003 23:34
> To: Cactus Developers List
> Subject: Problems with containers
>
> Hi Vincent and everyone else who is listening :-)
>
> while implementing and testing the <cactus> task I've been working on,
> I've encountered some problems with containers that I've not worked
very
> much with yet. (On the positive side, the task is now very nicely
> working with Tomcat3x, Tomcat4x and Resin2x).
cool :-)
>
> First problem is with Orion. I've tried both 1.6.0b and 2.0.1, but
both
> have the same problem with the filter redirector. First, as is
indicated
> in the test web.xml, the filter must be mapped to a "physical"
resource.
> If that isn't the case, or the resource doesn't exist in the web-app,
> Orion returns a "400 Bad Request". If it *is* mapped to an actual,
> existing resource, I get "java.net.SocketException: Connection aborted
> by peer: socket write error". Weird. Anyone running the filter tests
> successfully against Orion?
I had tried it with Orion 1.5.2 and 1.6.0 and it was working. I'll need
to try it again.
>
> Second is WebLogic, and is of course more complicated. I'm a complete
> newbie to WL, so I feel a bit lost. Should I expect to be able to run
> tests against WL-Server 7.0 SP2 out of the box? Obviously, I am not,
but
> that could easily be an error on my side ;-)
It was working for me with WL 6.1 SP3 and 7.0 SP1 if I recall correctly.
I haven't tried it with 7.0 SP2 though.
>
> More concretely, the problem I'm seeing is this:
>
------------------------------------------------------------------------
--
> ---
> test:
> [cactus] Building jar:
>
c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\application
s\
> test.war
> [cactus] Starting WebLogic Server...
> [cactus] <22.04.2003 23:04:38 CEST> <Notice> <Management> <140005>
> <Loading configuration
>
c:\DOKUME~1\chris\LOKALE~1\Temp\cactus\weblogic7x\testdomain\.\config.xm
l>
> [cactus] <22.04.2003 23:04:39 CEST> <Critical> <WebLogicServer>
> <000364> <Server failed during initialization.
> Exception:weblogic.management.configuration.ConfigurationException:
> Error parsing the configuration file: Version mismatch. have 30,
> expected 1 - with nested exception:
> [cactus] [weblogic.security.internal.SerializedSystemIniException:
> Version mismatch. have 30, expected 1]
> [cactus] weblogic.security.internal.SerializedSystemIniException:
> Version mismatch. have 30, expected 1
> [cactus] at
>
weblogic.security.internal.SerializedSystemIni.<init>(SerializedSystemIn
i.
> java:117)
> [cactus] at
>
weblogic.security.internal.SerializedSystemIni.getEncryptionService(Seri
al
> izedSystemIni.java:212)
> [cactus] at
>
weblogic.management.internal.EncryptedData.getEncryptionService(Encrypte
dD
> ata.java:82)
> [cactus] at
>
weblogic.management.internal.EncryptedData.decrypt(EncryptedData.java:44
)
>
------------------------------------------------------------------------
--
> ---
>
> It seems that the SerializedSystemIni.dat we provide includes version
> information, and WL detects an incompatibility. It seems weird to me
> that we're providing a binary, serialized file, as those are generally
> very fragile.
Sure. However, I could not find a working solution without this binary
file. One solution would be to either copy these files somewhere from
cactus.home.weblogic7x if available or generate them using some weblogic
command line tool. But I'm not sure how to do that unfortunately.
>
> WL 6.x doesn't seem to be available for download/evaluation anymore,
so
> I have absolutely no idea how to test that part of the container
> support. Any ideas?
You're right. They seem to be available only for past customers with
support contracts
(http://commerce.bea.com/siteinfo/previous_releases.jsp). So I say we
drop support for WL 6.x. Better to add support for the 8.x series... :-)
>
> Any input much appreciated, as always :-)
I'm not of much help. I haven't been playing with the latest containers
lately. This is one of the reasons I'd like to externalize container
configuration and start/stop/deploy from Cactus in the medium term and
put it in a project on its own. Maybe the new <cactus> Ant task
implementation could be used as the base for this new project once it is
finished (but of course keeping the Ant part in Cactus).
Thanks Chris!
-Vincent
>
> --
> Christopher Lenz
> /=/ cmlenz at gmx.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org